Set api call fails when kv versioning is not enabled and a new key is created

[rwthompsonii]

It may also fail during other times as well, but it definitely doesn't work in that configuration.

A line of documentation somewhere prominent that versioning is required would be nice.

[rwthompsonii]

for more details, i'm creating a key that doesn't exist in vault with kv2::set, and the "enable-versioning" stuff wasn't on, and the key would get written to vault but the response code is requiring a secrets metadata response and it gets .. nothing back if the versioning feature isn't enabled, so it barfs and fails the whole thing, even though the key is in the vault already.