fix: OpenViking sync-wave deadlock - move ExternalSecret ordering inside Application

Remove resource-level sync-wave annotations that caused ArgoCD deadlock.
The wave 8 annotation was meant for platform-level ordering (apps-of-apps)
but was incorrectly applied to individual resources within the Application.

This caused ArgoCD to apply Deployment (wave 0) before ExternalSecret (wave 8),
resulting in CreateContainerConfigError since the pod needed the secret first.

Changes:
- namespace.yaml: Remove sync-wave annotation, add clarifying comment
- externalsecret.yaml: Change sync-wave from 8 to -1 (must sync before Deployment at wave 0)
- application.yaml: Remove sync-wave annotation, document as platform-level only in comments

This ensures:
1. ExternalSecret syncs first (wave -1)
2. Deployment uses it immediately (implicit wave 0)
3. No deadlock

Task: t_3906c41a

cluster/platform/openviking/application.yaml

@@ -13,7 +13,11 @@ metadata:
   name: openviking
   namespace: argocd
   annotations:
-    argocd.argoproj.io/sync-wave: "8"
+    # Wave 8 (platform-level, apps-of-apps view): OpenViking Application syncs after Harbor (Wave 7)
+    # NOTE: This annotation controls the Application's position in the apps-of-apps rollout,
+    # NOT the ordering of resources within the Application. Internal resource ordering is
+    # controlled by sync-wave annotations on individual resources (ExternalSecret, etc.).
+    # argocd.argoproj.io/sync-wave: "8"  # Platform-level docs - NOT needed as annotation
     description: |
       OpenViking Platform Knowledge Infrastructure pilot deployment
       Pilot scope: Two corpora (hermes/ skills library, personal/homelab/)