Use RHEL upstream docker repo instead of abandoned centos

[kron4eg]

What this PR does / why we need it:
CentOS upstream docker repo being abandoned (naturally as CentOS8 is long time dead). This leads to errors where on rocky8 and rhel8 containerd 1.7 is not found. But it's actually present in RHEL repo!

What type of PR is this?
/kind bug

Special notes for your reviewer:

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

Use RHEL upstream docker repo instead of abandoned centos

Documentation:

NONE

[kron4eg]

/test pull-kubeone-e2e-aws-rockylinux-install-containerd-external-v1.30.1

[kron4eg]

/test pull-kubeone-e2e-aws-rhel-install-containerd-external-v1.30.1

[xmudrii]

/lgtm
/approve

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 289d089497395c9a5c2f43e4422e891c6c3f5f51

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

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 [xmudrii]

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

[xmudrii]

/cherrypick release/v1.8

[xmudrii]

/cherrypick release/v1.7

[kubermatic-bot]

@xmudrii: new pull request created: #3336

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.

[kubermatic-bot]

@xmudrii: #3316 failed to apply on top of branch "release/v1.7":

Applying: CentOS docker repo being abandoned, replaced with RHEL
Using index info to reconstruct a base tree...
M	pkg/scripts/render.go
M	pkg/scripts/testdata/TestKubeadmCentOS-cilium_cluster.golden
M	pkg/scripts/testdata/TestKubeadmCentOS-nutanix_cluster.golden
M	pkg/scripts/testdata/TestKubeadmCentOS-with_containerd.golden
M	pkg/scripts/testdata/TestKubeadmCentOS-with_containerd_with_insecure_registry.golden
M	pkg/scripts/testdata/TestUpgradeKubeadmAndCNICentOS.golden
M	pkg/scripts/testdata/TestUpgradeKubeletAndKubectlCentOS.golden
M	pkg/tasks/prerequisites.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/tasks/prerequisites.go
Auto-merging pkg/scripts/testdata/TestUpgradeKubeletAndKubectlCentOS.golden
CONFLICT (content): Merge conflict in pkg/scripts/testdata/TestUpgradeKubeletAndKubectlCentOS.golden
Auto-merging pkg/scripts/testdata/TestUpgradeKubeadmAndCNICentOS.golden
CONFLICT (content): Merge conflict in pkg/scripts/testdata/TestUpgradeKubeadmAndCNICentOS.golden
Auto-merging pkg/scripts/testdata/TestKubeadmCentOS-with_containerd_with_insecure_registry.golden
Auto-merging pkg/scripts/testdata/TestKubeadmCentOS-with_containerd.golden
Auto-merging pkg/scripts/testdata/TestKubeadmCentOS-nutanix_cluster.golden
CONFLICT (content): Merge conflict in pkg/scripts/testdata/TestKubeadmCentOS-nutanix_cluster.golden
Auto-merging pkg/scripts/testdata/TestKubeadmCentOS-cilium_cluster.golden
CONFLICT (content): Merge conflict in pkg/scripts/testdata/TestKubeadmCentOS-cilium_cluster.golden
Auto-merging pkg/scripts/render.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 CentOS docker repo being abandoned, replaced with RHEL
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release/v1.7

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.