fix(harnesses): migrate to ESO secrets_required form, mirror agent-runtimes

The CRS-served harnesses still carried `secrets_files: [{encrypted: true}]`
which now hard-fails on H-SECRET-1 ("SOPS-encrypted secrets_files entries
are no longer permitted") in the dispatcher's harness validator. Sync the
8 provider harnesses with the agent-runtimes copies: same `secrets_required`
shape, same `init.sh` (ESO-mounted file paths), same `bin/` wrappers.

Use bare `account_ref: "<provider>"` (not `<provider>.cp:cp` — that
scope-kind isn't valid per SR-DISP-1-FIELD).

Provider key names follow the per-provider schema as emitted by the CP
provisioner: minimax/airouter/z-ai → api_key; gitea-https/gitea-admin →
{token,base_url,username}; gitea-ssh* → {host,private_key}.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

harnesses/contexts/gitea-https/v1/harness.yaml

@@ -12,7 +12,8 @@ git_identity:
 scripts:
   init: "./init.sh"
 
-secrets_files:
-  - source: ./provider.sops.env
-    target: /opt/harness/secrets/gitea-https/provider.sops.env
-    encrypted: true
+secrets_required:
+  - name: gitea-https
+    account_ref: "gitea-https"
+    mount_path: /run/agent/secrets/gitea-https
+    mode: "0400"