/kind feature

Describe the solution you'd like

Currently the provider uses the default k8s ServiceAccount.

Please create a specific one, and:

• use it in the Deployment
• use it in the capv-leader-election-rolebinding RoleBinding`
• use it in the capv-manager-rolebinding ClusterRoleBinding

This will allow the provider to work when automountServiceAccountToken is set to false in the default ServiceAccount and in the created pods.

Anything else you would like to add:

Some references :

• https://kubeops.net/kubernetes-security-library/measures/36-best-practices-for-deactivating-auto-mount-and-managing-serviceaccounts
• New namespace serviceaccount/default with automountServiceAccountToken: false open-policy-agent/gatekeeper-library#192 (comment)

Environment:

• Cluster-api-provider-vsphere version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):