Adds rudimentary support for KV version 2 secret fetching
Update some upstream packages via go mod tidy; go mod vendor
NEW Tests for KV v2 fetching backed by a full-featured test cluster
The vault go api client doesn't discern between kv 1 and kv 2 as the vault binary is responsible for assembling the proper api paths to be called, so we must rely on DAYTONA consumers to do the same.
For example:
vault kv list secret/whatever is actually performing a list on secret/metadata/whatever. So a KV version 2 path walk in DAYTONA would be supplied as:
VAULT_SECRETS_MANY=secret/metadata/stuff, while a single secret is defined as VAULT_SECRET_SINGLE=secret/data/mysecret
The vault go api client doesn't discern between kv 1 and kv 2 as the vault binary is responsible for assembling the proper api paths to be called, so we must rely on DAYTONA consumers to do the same.
For example:
vault kv list secret/whateveris actually performing a list onsecret/metadata/whatever. So a KV version 2 path walk in DAYTONA would be supplied as:VAULT_SECRETS_MANY=secret/metadata/stuff, while a single secret is defined asVAULT_SECRET_SINGLE=secret/data/mysecret