new yaml is corrected based off of merge semantics; but the question is if we like these merge semantics

Signed-off-by: Yuval Kohavi <[email protected]>

Author: yuval-k

internal/kgateway/translator/gateway/testutils/outputs/traffic-policy/extauth.yaml

@@ -124,20 +124,6 @@ Listeners:
             grpcService:
               envoyGrpc:
                 clusterName: kube_infra_ext-authz_9000
-        - disabled: true
-          name: ext_auth/infra/section-name-gw-extauth
-          typedConfig:
-            '@type': type.googleapis.com/envoy.extensions.filters.http.ext_authz.v3.ExtAuthz
-            filterEnabledMetadata:
-              filter: dev.kgateway.disable_ext_auth
-              invert: true
-              path:
-              - key: extauth_disable
-              value:
-                boolMatch: true
-            grpcService:
-              envoyGrpc:
-                clusterName: kube_infra_ext-authz_9000
         - name: envoy.filters.http.router
           typedConfig:
             '@type': type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
@@ -263,9 +249,6 @@ Routes:
     ext_auth/infra/basic-gw-extauth:
       '@type': type.googleapis.com/envoy.config.route.v3.FilterConfig
       config: {}
-    ext_auth/infra/section-name-gw-extauth:
-      '@type': type.googleapis.com/envoy.config.route.v3.FilterConfig
-      config: {}
   virtualHosts:
   - domains:
     - tls.example.com