Patch vsphere CSI and CPI image registry to use registry.k8s.io

What does this MR do and why?

Patch the images used by vsphere-csi-driver and vsphere-cpi from the dismissed regitry gcr.io/cloud-provider-vsphere/release to the active ones registry.k8s.io/cloud-pv-vsphere/cloud-provider-vsphere registry.k8s.io/csi-vsphere/driver.

Note about k8s v1.27

The vsphere-cpi image for k8s v1.27.* registry.k8s.io/cloud-pv-vsphere/cloud-provider-vsphere:v1.27.0 hasn't been migrated upstream, so in order to continue to support it in Sylva I pushed it to registry.gitlab.com/sylva-projects/sylva-elements/container-images/sandbox-registry/cloud-provider-vsphere-cpi-release-manager:v1.27.0.

Related reference(s)

Closes #1796 (closed)

https://github.com/kubernetes/cloud-provider-vsphere#warning-kubernetes-image-registry-migration-for-cloud-provider-vsphere

Testing

Before:

$ kustomize build kustomize-units/vsphere-csi-driver | grep 'image:'
        image: registry.k8s.io/sig-storage/csi-attacher:v4.5.1
        image: registry.k8s.io/sig-storage/csi-resizer:v1.10.1
        image: gcr.io/cloud-provider-vsphere/csi/release/driver:v3.3.1
        image: registry.k8s.io/sig-storage/livenessprobe:v2.12.0
        image: gcr.io/cloud-provider-vsphere/csi/release/syncer:v3.3.1
        image: registry.k8s.io/sig-storage/csi-provisioner:v4.0.1
        image: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.2
        image: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.1
        image: gcr.io/cloud-provider-vsphere/csi/release/driver:v3.3.1
        image: registry.k8s.io/sig-storage/livenessprobe:v2.12.0
        image: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0
        image: gcr.io/cloud-provider-vsphere/csi/release/driver:v3.3.1
        image: registry.k8s.io/sig-storage/livenessprobe:v2.12.0

# vsphere-cpi with k8s_version_short={1.27,1.28,1.29}
$ helm template management-cluster charts/sylva-units -f charts/sylva-units/values.yaml -f charts/sylva-units/management.values.yaml -f environment-values/rke2-capv/values.yaml -f environment-values/rke2-capv/secrets.yaml -s templates/sylva-units-values.yaml | yq .stringData.values | yq .units.vsphere-cpi.helmrelease_spec.values.daemonset
null -> which defaults to [gcr.io/cloud-provider-vsphere/cpi/release/manager](https://github.com/kubernetes/cloud-provider-vsphere/blob/85b38cd5858e0a6ac9a17b7ce5658957d24dd399/charts/vsphere-cpi/values.yaml#L57C10-L57C59)

After this mr:

$ kustomize build kustomize-units/vsphere-csi-driver | grep 'image:'
        image: registry.k8s.io/sig-storage/csi-attacher:v4.5.1
        image: registry.k8s.io/sig-storage/csi-resizer:v1.10.1
        image: registry.k8s.io/csi-vsphere/driver:v3.3.1
        image: registry.k8s.io/sig-storage/livenessprobe:v2.12.0
        image: registry.k8s.io/csi-vsphere/syncer:v3.3.1
        image: registry.k8s.io/sig-storage/csi-provisioner:v4.0.1
        image: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.2
        image: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.1
        image: registry.k8s.io/csi-vsphere/driver:v3.3.1
        image: registry.k8s.io/sig-storage/livenessprobe:v2.12.0
        image: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0
        image: registry.k8s.io/csi-vsphere/driver:v3.3.1
        image: registry.k8s.io/sig-storage/livenessprobe:v2.12.0

# vsphere-cpi with k8s_version_short={1.28,1.29}
$ helm template management-cluster charts/sylva-units -f charts/sylva-units/values.yaml -f charts/sylva-units/management.values.yaml -f environment-values/rke2-capv/values.yaml -f environment-values/rke2-capv/secrets.yaml -s templates/sylva-units-values.yaml | yq .stringData.values | yq .units.vsphere-cpi.helmrelease_spec.values.daemonset
image: registry.k8s.io/cloud-pv-vsphere/cloud-provider-vsphere

# vsphere-cpi with k8s_version_short=1.27
$ helm template management-cluster charts/sylva-units -f charts/sylva-units/values.yaml -f charts/sylva-units/management.values.yaml -f environment-values/rke2-capv/values.yaml -f environment-values/rke2-capv/secrets.yaml -s templates/sylva-units-values.yaml | yq .stringData.values | yq .units.vsphere-cpi.helmrelease_spec.values.daemonset
image: registry.gitlab.com/sylva-projects/sylva-elements/container-images/sandbox-registry/cloud-provider-vsphere-cpi-release-manager