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/application.yaml

@@ -0,0 +1,40 @@
+# ------------------------------------------------------------------------------
+# Platform: harbor (Container Registry)
+# Theme: the-seas (EPCOT: The Seas with Nemo & Friends)
+# Wave 7 — depends on Gateway API (wave 4), cert-manager (wave 3), ESO (wave 1)
+# Multi-source: Helm chart from upstream + values + manifests from repo
+# ------------------------------------------------------------------------------
+apiVersion: argoproj.io/v1alpha1
+kind: Application
+metadata:
+  name: harbor
+  namespace: argocd
+  annotations:
+    argocd.argoproj.io/sync-wave: "7"
+spec:
+  project: default
+  sources:
+    # Source 1: Helm chart from upstream Harbor repository
+    - repoURL: https://helm.goharbor.io
+      chart: harbor
+      targetRevision: 1.19.1
+      helm:
+        valueFiles:
+          - $values/cluster/platform/harbor/values.yaml
+    # Source 2: Repo — values ref + ExternalSecret + HTTPRoutes + Certificates
+    - repoURL: https://gitea.mk-labs.cloud/rblundon/homelab.git
+      targetRevision: main
+      path: cluster/platform/harbor
+      ref: values
+      directory:
+        exclude: "application.yaml"
+  destination:
+    server: https://kubernetes.default.svc
+    namespace: harbor
+  syncPolicy:
+    automated:
+      prune: true
+      selfHeal: true
+    syncOptions:
+      - CreateNamespace=true
+      - ServerSideApply=true