feat(devel): enable vault persistence in dev mode

[migmartri]

It enables persistence in Vault when ran in development mode both in local and in k8s, note: in development mode

Docker Compose (devel/)

• Switch Vault from dev mode to server mode with file storage backend
• Add vault-config.hcl for server configuration
• Add vault-init.sh script to handle initialization, unsealing, and token creation
• Mount persistent volume for Vault data
• Automatically unseal Vault on startup
• Create 'notasecret' token for development convenience
• Enable KV v2 secrets engine

Helm Chart (deployment/chainloop/)

• Add init script via vault.extraDeploy in parent chart values
• Configure file storage backend (overrides subchart defaults)
• Auto-initialize and unseal Vault on pod start
• Validate init.txt content to handle corrupted files
• Create 'notasecret' token if it doesn't exist
• Enable KV v2 secrets engine (required by controlplane)
• All configuration in parent chart (no subchart modifications)

Benefits

• Data persists across container/pod restarts
• Maintains development convenience (auto-unseal, known token)
• No manual intervention required after restart
• Consistent behavior between Docker Compose and Helm deployments

Fixes #2574"