ReadSecretPathsAsync to also support GET Method

[greg-signi]

Describe the feature requesInt or question Having problems with the LIST method using istio-proxy, which currently doesn't allow the custom http method LIST, more specifically in this request

        public async Task<Secret<ListInfo>> ReadSecretPathsAsync(string path, string mountPoint = null, string wrapTimeToLive = null)
        {
            Checker.NotNull(path, "path");

            return await _polymath.MakeVaultApiRequest<Secret<ListInfo>>(mountPoint ?? _polymath.VaultClientSettings.SecretsEngineMountPoints.KeyValueV2, "/metadata/" + path.Trim('/'), _polymath.ListHttpMethod, wrapTimeToLive: wrapTimeToLive).ConfigureAwait(_polymath.VaultClientSettings.ContinueAsyncTasksOnCapturedContext);
        }

Additional context

Vault supports both LIST & GET, can you add an option or something for us to be able to make the http request with the GET method ?

[greg-signi]

@rajanadar do you have any thoughts on this ?

[konidev20]

@greg-signi , let me see what I can do

[konidev20]

Found the documentation for reference:

The API documentation uses LIST as the HTTP verb, but you can still use GET with the ?list=true query string.

Ref: https://developer.hashicorp.com/vault/api-docs#api-operations

[konidev20]

Hey @rajanadar,

Should we do this for other endpoints as well? I see that since LIST is not a standard HTTP method, it might cause issues for other folks as well.

I remember, @hoerup advising me not to use HTTP LIST in a previous PR that I had raised (https://github.com/rajanadar/VaultSharp/pull/246#issuecomment-1129025496).

[greg-signi]

@konidev20 thank you thank you 💯

[konidev20]

Hey @greg-signi, You can take a build from the branch and test if it works.

[greg-signi]

Hey @konidev20 Yep appears to be working fine 👍