Update vSphere images to use upstream image repository or our mirror

[xmudrii]

What this PR does / why we need it:

This PR replaces the registry used for vSphere CCM and CSI images. Unfortunately:

• The new vSphere CCM image registry has images only starting from v1.28.0
• There are no images in the new official vSphere CSI image registry at the moment

Because of that, we unfortunately have to resort to the mirroring the old/unavailable images.

Which issue(s) this PR fixes:
xref #3375

What type of PR is this?
/kind bug
/kind regression
/priority critical-urgent

Does this PR introduce a user-facing change? Then add your Release Note here:

[ACTION REQUIRED] Fix vSphere CCM and CSI images. The CCM images for versions starting with v1.28.0 are pulled from the new community-owned image repository. The CCM images for versions prior to v1.28.0, and the CSI images, are pulled from the Kubermatic-managed mirror on `quay.io`. If you have a vSphere cluster, we strongly recommend upgrading to the latest KubeOne patch release and running `kubeone apply` **as soon as possible**, because the old image repository (`gcr.io/cloud-provider-vsphere`) is not available anymore, hence it's not possible to pull the needed images from that repository

Documentation:

TBD

[xmudrii]

/test pull-kubeone-e2e-vsphere-default-install-containerd-external-v1.28.13

[xmudrii]

/cherrypick release/v1.8

[kubermatic-bot]

@xmudrii: once the present PR merges, I will cherry-pick it on top of release/v1.8 in a new PR and assign it to you.

In response to this:

/cherrypick release/v1.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kron4eg]

/lgtm
/approve

[kubermatic-bot]

LGTM label has been added.

Git tree hash: add88950e7e4d31885d3cc219a904c6d2e383218

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kron4eg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[xmudrii]

/retest

[kubermatic-triage-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[xmudrii]

/override pull-kubeone-e2e-vsphere-default-install-containerd-external-v1.28.13
Testing manually

[kubermatic-bot]

@xmudrii: Overrode contexts on behalf of xmudrii: pull-kubeone-e2e-vsphere-default-install-containerd-external-v1.28.13

In response to this:

/override pull-kubeone-e2e-vsphere-default-install-containerd-external-v1.28.13
Testing manually

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kubermatic-bot]

@xmudrii: new pull request could not be created: failed to create pull request against kubermatic/kubeone#release/v1.8 from head kubermatic-bot:cherry-pick-3376-to-release/v1.8: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between kubermatic:release/v1.8 and kubermatic-bot:cherry-pick-3376-to-release/v1.8"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherrypick release/v1.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.