feat(couchdb): split internal/external ingress for correct CN per cert

- values.yaml: internal ingress only (communicore.local.mk-labs.cloud)
  CN=communicore.local.mk-labs.cloud, secret=couchdb-tls
- ingress-public.yaml: external ingress (communicore.mk-labs.cloud)
  CN=communicore.mk-labs.cloud, secret=couchdb-tls-public
  ExternalDNS opt-in annotations for Cloudflare -> ingress.mk-labs.cloud

Obsidian Sync connects externally via communicore.mk-labs.cloud;
JARVIS traffic stays internal on communicore.local.mk-labs.cloud.

cluster/applications/couchdb/values.yaml

@@ -53,24 +53,21 @@ service:
   type: ClusterIP
   port: 5984
 
-# Ingress configuration
+# Ingress configuration — internal only
+# External access via separate ingress manifest (ingress-public.yaml)
+# which carries its own cert with CN=communicore.mk-labs.cloud
 ingress:
   enabled: true
   className: nginx
   annotations:
     cert-manager.io/cluster-issuer: "letsencrypt-prod"
     external-dns.alpha.kubernetes.io/hostname: "communicore.local.mk-labs.cloud"
-    external-dns.alpha.kubernetes.io/target: "ingress.mk-labs.cloud"
-    # Opt in to public Cloudflare DNS — creates communicore.mk-labs.cloud -> ingress.mk-labs.cloud
-    external-dns.alpha.kubernetes.io/public: "true"
   hosts:
     - communicore.local.mk-labs.cloud
-    - communicore.mk-labs.cloud
   tls:
     - secretName: couchdb-tls
       hosts:
         - communicore.local.mk-labs.cloud
-        - communicore.mk-labs.cloud
 
 # Resource limits
 resources: