fix(harbor): correct naming convention and use staging certs

- Rename application/namespace: the-seas -> harbor
- Move directory: cluster/platform/the-seas -> cluster/platform/harbor
- Update all resource references (ExternalSecret, HTTPRoutes, Certificates)
- Switch to letsencrypt-staging issuer (avoid ACME rate limits during testing)
- Thematic name 'the-seas' remains in DNS hostnames and comments

cluster/platform/harbor/httproute.yaml

@@ -0,0 +1,32 @@
+# ------------------------------------------------------------------------------
+# HTTPRoute — Harbor (Primary) via Cilium Gateway
+# Primary DNS: the-seas.local.mk-labs.cloud (EPCOT theme)
+# ------------------------------------------------------------------------------
+apiVersion: gateway.networking.k8s.io/v1
+kind: HTTPRoute
+metadata:
+  name: harbor-the-seas
+  namespace: harbor
+  annotations:
+    external-dns.alpha.kubernetes.io/hostname: the-seas.local.mk-labs.cloud
+    external-dns.alpha.kubernetes.io/target: "10.1.71.90"
+spec:
+  parentRefs:
+    - group: gateway.networking.k8s.io
+      kind: Gateway
+      name: fastpass-gateway
+      namespace: gateway
+      sectionName: https
+  hostnames:
+    - the-seas.local.mk-labs.cloud
+  rules:
+    - matches:
+        - path:
+            type: PathPrefix
+            value: /
+      backendRefs:
+        - group: ""
+          kind: Service
+          name: harbor
+          port: 80
+          weight: 1