Problem Statement

When using a ReadOnly type token, the pod crashes because of a log failure in de vault-cli.
Also when validating the store, the Provider always tried to get the list of secrets which is not allowed with a ReadOnly token. This will now get the token info endpoint and save the type of token for future reference when we're implementing writing and creating secrets also.

The Previder vault support 2 types of tokens to manage/read secrets.
ReadWrite has the following privileges:

• List, read, update, remove secrets
• Decrypt secret by id

ReadOnly token has the next privilege:

• Decrypt secret by id

The ReadOnly token is meant for in-cluster use for enhanced security, but is not allowed to List secrets. The current code calls the GetSecrets method which always errors out with a 401 Unauthorized for a ReadOnly and should not be used for validating the store.
Instead we changed it to the GetTokenInfo method which returns information about the current used token. This is the only call that will work for both kind of tokens.

The version of the client has already been updated in another PR, in version 0.1.2 we logged using "log.Fatal" when a 401 was thrown, which killed the daemon when using a ReadOnly token. This has been fixed to a proper log line in 0.1.3.

Checklist

• I have read the contribution guidelines
• All commits are signed with git commit --signoff
• My changes have reasonable test coverage
• All tests pass with make test
• I ensured my PR is ready for review with make reviewable