Startup secrets keys created in lowercase

[akijakya]

Bugs should be filed for issues encountered whilst operating bank-vaults.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
The latest version of bank-vaults creates startup secrets, but they appear in lowercase in Vault resulting in vault-env not finding them when applying our default resources we use for testing.

Expected behaviour:
Getting this:

vault kv get secret/accounts/aws
Handling connection for 8200
====== Secret Path ======
secret/data/accounts/aws

======= Metadata =======
Key                Value
---                -----
created_time       2023-06-28T09:21:21.574452303Z
custom_metadata    <nil>
deletion_time      n/a
destroyed          false
version            1

============ Data ============
Key                      Value
---                      -----
AWS_ACCESS_KEY_ID        secretId
AWS_SECRET_ACCESS_KEY    s3cr3t

instead of this:

vault kv get secret/accounts/aws
Handling connection for 8200
====== Secret Path ======
secret/data/accounts/aws

======= Metadata =======
Key                Value
---                -----
created_time       2023-06-28T08:48:28.447984417Z
custom_metadata    <nil>
deletion_time      n/a
destroyed          false
version            1

============ Data ============
Key                      Value
---                      -----
aws_access_key_id        secretId
aws_secret_access_key    s3cr3t

/kind bug

[akijakya]

The issue was introduced by a viper version upgrade, turns out it was a bug that it allowed uppercase characters in the first place (see issue). Short term solution is to revert the upgrade.