feat: configure External Secrets with Vault backend and enable Jenkins secret synchronization

manifest/jenkins/values.yaml

@@ -97,17 +97,17 @@ controller:
     # The default configuration uses this secret to configure an admin user
     # If you don't need that user or use a different security realm, then you can disable it
     # -- Must stay true so the controller mounts the admin Secret; when existingSecret is set, the chart does not create that Secret (supply it yourself or via externalSecret).
-    createSecret: true
+    createSecret: false
 
     # -- If set, chart does not create the admin Secret; you must create it (e.g. kubectl) or use externalSecret (requires ESO CRDs on the cluster).
     existingSecret: ""
 
     # -- Emits external-secrets.io/v1beta1 ExternalSecret (needs External Secrets Operator installed). Helm cannot talk to Vault without it or another sync mechanism.
     externalSecret:
-      enabled: false
+      enabled: true
       refreshInterval: 1h
       secretStoreRef:
-        name: vault
+        name: vault-backend
         kind: ClusterSecretStore
       remoteRef:
         # Vault KV v2 secret name under the store mount (your UI path: Secrets / kv / jenkins-admin-password)