Revert bumping kubernetes-cni to v1.2.0 and cri-tools to v1.26.0

[xmudrii]

What type of PR is this?

/kind regression

What this PR does / why we need it:

We bumped the minimum kubernetes-cni version to v1.2.0 in #2863, and cri-tools to v1.26.0 in #2821. However, this affects all kubelet and kubeadm packages, including v1.23.16, v1.24.10, v1.25.6, and v1.26.1.

This brings two major problems:

• cri-tools v1.26.0 requires containerd 1.6, but many users are still using containerd 1.5, so they are now forced to upgrade
• users are confused are cni-plugins v1.2.0 compatible with older minor releases
  • I'm also not sure that we properly or at all tested that

Therefore, we think it might be better to revert those bumps. This problem will be solved in the future with the KEP-1731 (kubernetes/enhancements#1731).

Which issue(s) this PR fixes:

Fixes #2866

Does this PR introduce a user-facing change?

Revert increasing the minimum kubernetes-cni and cri-tools versions

/assign @saschagrunert
cc @kubernetes/release-engineering

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert, 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 [saschagrunert,xmudrii]

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

[dkoshkin]

Thank you for this fix! Are there plans to remove the kubernetes-cni v1.2.0 and cri-tools v1.26.0 packages from the repos?

Currently I still see it (atleast in the Deb repo) which means when kubeadm is installed it will bring these new versions with it, since they are the latest and there are not upper bounds.

[xmudrii]

We don't have such plans as of now and I'm also not sure if it is even technically feasible to remove packages. There are a few important notes regarding this PR:

• This will be in effect starting with the February patch releases. We can't amend existing releases, so if this is an issue for you, we recommend staying on previous patch releases until February patch releases
• We can't remove existing packages, but you will be able to manually bind to a lower version. For example, you will be able to do something like this: apt-get install kubeadm kubelet kubernetes-cni=1.1.1* cri-tools=1.25.0*