Allow using multiple KV stores

[hmrks]

This PR adds support for multiple KV stores as backends in Vault, increasing flexibility for a wider range of secret-management workflows. This could be useful in a number of scenarios.

Use cases:

• Independent team/department vaults: different teams or departments can use wildly different paths in Vault.
• Hybrid personal/team vaults: run one backend for personal secrets and another for team-shared secrets, keeping policies and permissions neatly separated.

To implement this, each entry in secretList now has both the store path and the secret name in a single string, separated by the delimiter ##. At login time, you can add as many KV stores as you like:

After authenticating, you can activate or deactivate individual secrets from any of your configured backends:

[hmrks]

Hi @mulbc! Not trying to push you, just checking in on this PR. Ping me in case there's anything I can do to help. 🙂

Thanks again for your time and for maintaining this project! 🙏