config: removing deprecated bind_to_port (#5288)

Risk Level: Medium (higher risk than average of build breakage on merge)
Testing: existing tests pass
Docs Changes: n/a
Release Notes: n/a

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Mirrored from https://github.com/envoyproxy/envoy @ 36db7761cc963a7790eb31eb7bccd7cfb248146c

envoy/api/v2/lds.proto

@@ -86,21 +86,7 @@ message Listener {
   // Listener metadata.
   core.Metadata metadata = 6;
 
-  // [#not-implemented-hide:]
-  message DeprecatedV1 {
-    // Whether the listener should bind to the port. A listener that doesn’t
-    // bind can only receive connections redirected from other listeners that
-    // set use_original_dst parameter to true. Default is true.
-    //
-    // [V2-API-DIFF] This is deprecated in v2, all Listeners will bind to their
-    // port. An additional filter chain must be created for every original
-    // destination port this listener may redirect to in v2, with the original
-    // port specified in the FilterChainMatch destination_port field.
-    google.protobuf.BoolValue bind_to_port = 1;
-  }
-
-  // [#not-implemented-hide:]
-  DeprecatedV1 deprecated_v1 = 7;
+  reserved 7;
 
   enum DrainType {
     // Drain in response to calling /healthcheck/fail admin endpoint (along with the health check