Source the control plane from Vault and use a stable ref name

Two hardcoded values tied this repo to one specific Konnect org, and
replacing that org broke both.

CONTROL_PLANE_ID was pasted into gateway-kustomization.yaml. It now
comes from Vault through External Secrets, into a Secret in flux-system
that postBuild.substituteFrom reads. flux-system is acceptable for the
id — it is visible in the Konnect UI URL — but not for the token, which
keeps going straight to the domain namespace as before.

CONTROL_PLANE_REF_NAME held the random suffix the Gateway operator gives
its auto-created mirror CR, looked up by hand. The new org recreated
those CRs under new suffixes, so the ref named an object that no longer
existed and the domain's Kong entities sat Programmed=False. It now
names the ${NAME}-cp mirror declared in k8s-platform's
dataplane-template — derived from NAME, stable across Gateway
recreations and org changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

dev/api-gateway/policies-kustomization.yaml

@@ -19,13 +19,10 @@ spec:
     substitute:
       NAME: catalog-dev
       NAMESPACE: catalog
-      # Looked up manually after gateway-kustomization.yaml's
-      # Gateway/GatewayConfiguration first reconciled — the operator
-      # auto-names the mirrored KonnectGatewayControlPlane with a random
-      # suffix, not derivable from NAME. See
-      # dataplane-globalpolicy-template/global-policies-pluginbindings.yaml's
-      # comment. Automate this lookup once the self-service pipeline exists.
-      CONTROL_PLANE_REF_NAME: catalog-dev-bkphl
+      # Stable by construction: the mirror CR is declared with this derived
+      # name in k8s-platform/dataplane-template/controlplane-mirror.yaml, so
+      # it no longer has to be looked up after each Gateway reconcile.
+      CONTROL_PLANE_REF_NAME: catalog-dev-cp
       # Every audience valid anywhere in the catalog domain — grows as the
       # domain gains APIs.
       JWT_AUDIENCE_WHITELIST: '["catalog-api", "mcp-catalog"]'