Bump CAPV provider due to unavailable CPI/CSI images

[thehejik]

What steps did you take and what happened?

After provisioning CAPV RKE2 cluster by using dev turtles (post 0.15.0) with vsphere infra provider v1.11.3 I noticed that vsphere-csi pods are in Imagepullbackoff state and not ready. Problem is that some images are not available anymore.

Upstream issue https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/3199 (not linking)

Failed to pull image "gcr.io/cloud-provider-vsphere/csi/release/driver:v2.1.0": failed to pull and unpack image "gcr.io/cloud-provider-vsphere/csi/release/driver:v2.1.0": failed to resolve reference "gcr.io/cloud-provider-vsphere/csi/release/driver:v2.1.0": failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://gcr.io/v2/token?scope=repository%3Acloud-provider-vsphere%2Fcsi%2Frelease%2Fdriver%3Apull&service=gcr.io: 401 Unauthorized

/kind bug

[thehejik]

Two images that are not available:

gcr.io/cloud-provider-vsphere/csi/release/driver:v2.1.0
gcr.io/cloud-provider-vsphere/csi/release/syncer:v2.1.0

According to @alexander-demicev the fix should be just about changing image references in https://github.com/rancher/cluster-api-provider-rke2/blob/main/examples/vmware/cluster-template.yaml

[thehejik]

Before closing, could we also update our e2e template here?