Do not register ClientTrafficPolicy with control plane.

Due to limitations in how Envoy Gateway programs listeners,
a ClientTrafficPolicy cannot be applied to non-TLS listeners
with overlapping ports. Application to TLS listeners works
without issue, however the inconsistency is undesirable.

Future TLS settings can be provided via the Gateway Listener's
TLS configuration.

Header manipulation, while not "early", can be accomplished
today via `RequestHeaderModifier` filters. Timeouts can
also be defined in existing route rules.

Remaining features are mostly around tuning, where there can
be generous defaults set on the platform.

Author: joshlreese

config/crd/gateway/kustomization.yaml

@@ -51,3 +51,9 @@ patches:
       kind: CustomResourceDefinition
       metadata:
         name: envoyproxies.gateway.envoyproxy.io
+  - patch: |
+      $patch: delete
+      apiVersion: apiextensions.k8s.io/v1
+      kind: CustomResourceDefinition
+      metadata:
+        name: clienttrafficpolicies.gateway.envoyproxy.io