EVE AppInst Discovery: move allow_to_discover to AppInst port

This is more granular approach. From appInstance perspective,
you also know which network port will be used.

Signed-off-by: Pavel Abramov <uncle.decart@gmail.com>

proto/config/appconfig.proto

@@ -103,6 +103,9 @@ message SnapshotConfig {
 // can also be increased to cause an application instance restart without
 // any other change to the application instance.
 message AppInstanceConfig {
+  // deprecated fields
+  reserved 14, 24;
+
   UUIDandVersion uuidandversion = 1;
   string displayname = 2; // User-friendly name
   VmConfig fixedresources = 3;
@@ -206,10 +209,6 @@ message AppInstanceConfig {
 
   // PatchEnvelopeRef is used to track all patch envelopes used by the app instance
   PatchEnvelopeRef patchRef = 23;
-
-  // allow AppInstance to discover other AppInstances
-  // attached to its network instances
-  bool allow_to_discover = 24;
 }
 
 message PatchEnvelopeRef {

proto/config/netconfig.proto

@@ -55,6 +55,10 @@ message NetworkAdapter {
   // valid vlan id range: 2 - 4093
   // vlan id 1 is implicitly used by linux bridges
   uint32 access_vlan_id = 41;
+
+  // allow AppInstance to discover other AppInstances
+  // attached to this network instance. Default is false
+  bool allow_to_discover = 42;
 }
 
 message WirelessConfig {