docs: stop naming the middleware

An agent talks to URLs that honour a contract: an MCP endpoint, an OIDC token
endpoint, an OpenAI-shaped LLM endpoint. Whatever serves those URLs is
replaceable, and naming it in an agent's code or docs implies a coupling that
does not exist.

Every product name is gone from prose, comments and identifiers, replaced by
what the agent actually depends on. Where a behaviour of the current middleware
leaks into the contract — the second audience scope, the tool ACL — the text
now says what the caller must do and why, not who imposes it.

One string survives and cannot be fixed here: the broker client an agent must
name in its audience scopes is itself named after the middleware. Closing that
means renaming it in Keycloak and following the rename through the gateway
configuration and LibreChat. Recorded as a blocker.

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

dev/gitrepository.yaml

@@ -1,12 +1,11 @@
-# HTTPS with no credentials, unlike the kong-* repos which use SSH and a deploy
-# key from Vault. Deliberate: this repo is already anonymously readable over
+# HTTPS with no credentials, unlike the platform repos which use SSH and a
+# deploy key from Vault. Deliberate: this repo is already anonymously readable over
 # HTTPS on gitea, so a deploy key would guard nothing while adding a Vault entry
 # and a gitea key to create by hand before anything deploys. TLS still gives
 # integrity and authenticity of the source.
 #
 # If the gitea repos are ever made private, this becomes an SSH sourceRef with
-# an ExternalSecret holding the deploy key — the pattern in
-# kong-catalog-api/dev/.
+# an ExternalSecret holding the deploy key — the pattern the platform repos use.
 apiVersion: source.toolkit.fluxcd.io/v1
 kind: GitRepository
 metadata: