Add new role parameter to specify the k8s role ref type

[refucktor]

Overview

What is the change?

• Add a new parameter to the vault k8s secrets role allowing to specify the type (Role / ClusterRole) of the role reference used in the final RoleBinding / ClusterRoleBinding

Why is the change needed?
The reasons are explained in this issue hashicorp/vault/issues/25579
As a summary, if I want to use a k8s ClusterRole in the kubernetes_role_name but the vault secrets role has the parameter kubernetes_role_type set to Role, then the final RoleBinding is using a Role in the ref, therefore the binding is incorrect

Design of Change

How was this change implemented?

• Add a new parameter to the Vault K8s Secrets Role called kubernetes_role_ref_type with possible values Role or ClusterRole
• During secrets role creation, the value for the new parameter will be set to match the parameter kubernetes_role_type
• During the credentials creation for the workflow where the kubernetes_role_name is specified, the RoleRef used in the binding take the new parameter (kubernetes_role_ref_type) to populate the type

Related Issues/Pull Requests

[x] hashicorp/vault Issue #25579
[x] hashicorp/vault-plugin-secrets-kubernetes Issue #48

Contributor Checklist

[x] Add relevant docs to upstream Vault repository, or sufficient reasoning why docs won’t be added yet
Vault Docs PR
[ ] Add output for any tests not ran in CI to the PR description (eg, acceptance tests)
[x] Backwards compatible

[hashicorp-cla]

All committers have signed the CLA.

[refucktor]

any update on this topic???