Remove redundant Harbor manifest files

Harbor Helm chart creates Ingress and cert-manager auto-creates certificates
via Ingress annotations. Removed non-functional and redundant manifests:

- certificate.yaml: cert-manager creates from Ingress annotation
- httproute.yaml: non-functional (pointed to non-existent service)
- httproute-alt.yaml: non-functional (pointed to non-existent service)

Standardized on single hostname: the-seas.local.mk-labs.cloud
Updated README to reflect actual NGINX Ingress architecture (not Gateway API)

Net: -97 lines, simplified deployment, no functional change

cluster/platform/harbor/README.md

@@ -10,9 +10,8 @@ Harbor is an open-source container registry that provides trust, compliance, per
 
 ## Service Details
 
-- **Primary URL:** https://the-seas.local.mk-labs.cloud
-- **Alternate URL:** https://harbor.local.mk-labs.cloud (for intuitive `docker login harbor...`)
-- **Namespace:** the-seas
+- **URL:** https://the-seas.local.mk-labs.cloud
+- **Namespace:** harbor
 - **Sync Wave:** 7 (deploys after Gateway API, cert-manager, ExternalSecrets)
 
 ## Architecture
@@ -88,23 +87,21 @@ All credentials are stored in 1Password and synchronized to Kubernetes via Exter
 
 ## Network & TLS
 
-### DNS Names
-- **Primary:** the-seas.local.mk-labs.cloud
-- **Alternate:** harbor.local.mk-labs.cloud
+### DNS Name
+- **Hostname:** the-seas.local.mk-labs.cloud
 
-Both DNS names resolve to the Cilium Gateway IP (10.1.71.90) via external-dns.
+DNS resolves to the NGINX Ingress Controller IP (10.1.71.80).
 
-### TLS Certificates
-- Issued by Let's Encrypt (letsencrypt-prod ClusterIssuer)
-- Managed by cert-manager
-- Separate certificates for each hostname
-- Stored as Kubernetes secrets: `the-seas-tls`, `harbor-tls`
+### TLS Certificate
+- Issued by Let's Encrypt (letsencrypt-staging ClusterIssuer)
+- Managed by cert-manager (automatic via Ingress annotation)
+- Certificate stored as Kubernetes secret: `harbor-tls`
 
 ### Routing
-- **Gateway:** fastpass-gateway (namespace: gateway)
+- **Ingress Controller:** NGINX (nginx-ingress)
 - **Protocol:** HTTPS (port 443)
-- **Backend:** ClusterIP service `the-seas` on port 80
-- TLS termination at Gateway level
+- **Backend:** Harbor NGINX service on port 80
+- TLS termination at Ingress level
 
 ## Access & Authentication