rename: homelab-gateway → telegram-gateway

Aligns the project name with the public URL (tg.arcodange.fr) and the
Arcodange organization conventions. The 'homelab-gateway' name was too
generic.

Touches: chart name + helpers, image registry path, Go module path,
secret/configmap names, deployment mountPath, all docs.

chart/values.yaml

@@ -1,7 +1,7 @@
 replicaCount: 1
 
 image:
-  repository: gitea.arcodange.lab/arcodange/homelab-gateway
+  repository: gitea.arcodange.lab/arcodange/telegram-gateway
   pullPolicy: Always
   tag: ""
 
@@ -85,18 +85,18 @@ bots:
     handler: echo
 
 # k8s Secret consumed by `envFrom`. Phase 1: create it manually with kubectl.
-#   kubectl -n homelab-gateway create secret generic homelab-gateway-bots \
+#   kubectl -n telegram-gateway create secret generic telegram-gateway-bots \
 #     --from-literal=BOT_FACTORY_TOKEN=…   --from-literal=BOT_FACTORY_SECRET=…
 secret:
-  name: homelab-gateway-bots
+  name: telegram-gateway-bots
 
 # Vault Secrets Operator integration (Phase 2+). When enabled, VSO writes the
-# secret named `secret.name` automatically from `kvv2/homelab-gateway/config`.
+# secret named `secret.name` automatically from `kvv2/telegram-gateway/config`.
 vault:
   enabled: false
-  role: homelab-gateway
+  role: telegram-gateway
   mount: kvv2
-  path: homelab-gateway/config
+  path: telegram-gateway/config
   refreshAfter: 30s
 
 nodeSelector: