Rename back to catalogue-agent; stop owning the shared namespace

catalog-agent was one rename too aggressive: 'catalogue' is accepted, and the
Keycloak client, its audience scope and the Vault key that names it were never
renamed to match — leaving an inconsistency between what Kubernetes and
Keycloak call the same agent. Keycloak carries more weight to move, so this
side moves back.

k8s/namespace.yaml is out of this Kustomization's inventory. It was in
2026-08-31 when renaming the Kustomization pruned the old one — which owned
the namespace three agents share — and took all three down. A namespace shared
across repos should not be owned by any one of them.

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

k8s/externalsecret.yaml

@@ -8,7 +8,7 @@
 apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
-  name: catalog-agent-secrets
+  name: catalogue-agent-secrets
   namespace: agents
 spec:
   refreshInterval: 1h
@@ -16,7 +16,7 @@ spec:
     kind: ClusterSecretStore
     name: vault-keycloak
   target:
-    name: catalog-agent-secrets
+    name: catalogue-agent-secrets
   data:
     - secretKey: CATALOGUE_CLIENT_SECRET
       remoteRef: