Test if using cri-dockerd v0.3.5 removes the need for forked kubelet

[superseb]

As described in https://github.com/rancher/hyperkube#kubelet-binary-source-change, we are currently using a forked repository to generate the kubelet to solve this issue (rancher/rancher#38816).

It was filed upstream earlier, but it seems that in v0.3.5, a PR was merged to solve this issue.

We should test if using upstream kubelet binary and cri-dockerd v0.3.5 solves the issue so we can remove the need for our fork.

[kinarashah]

Process wise, we would introduce a new k8s version in KDM (dev branch or forked, would need a new rke-tools branch if not using forked repo) that uses new cri-dockerd, and run the following tests: rancher/rancher#38816 (comment)
rancher/rancher#38816 (comment)

Note that the PR in cri-dockerd is new code change and doesn't fallback to the old behavior, so the performance won't be exactly identical but should be better than the original v1.24.10-rancher1-1 where the issue was first reported. We can compare metrics and then decide if we can rid of the forked kubelet or temporarily deliver both k8s versions (with and without forked kubelet) for users to test it out.

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[kinarashah]

Commenting for bot

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.