UI/fix kv data cache

[hashishaw]

This PR fixes some strange behavior within the KV secrets engine (see gifs below):

User reader has the following policy:

path "kv/metadata" {
  capabilities = ["list"]
}
path "kv/data/*" {
  capabilities = ["read", "update"]
}

User admin has the following policy:

path "kv/metadata" {
  capabilities = ["list"]
}
path "kv/data/*" {
  capabilities = ["read", "update"]
}
path "kv/metadata/*" {
  capabilities = ["read", "update"]
}

BEFORE: reader cannot click button create new version, but experiences no issues when creating a version other than the new version doesn't show after redirect to show view

AFTER: admin can still create new version from specific version (this behavior is preserved, if user has metadata read access)

AFTER: reader can create new version, and it always creates from the most recent version due to no metadata read access

[Monkeychip]

Thanks for tackling this!