fix(defaults): wrong cri_socket path for containerd

[maxime1907]

What type of PR is this?
/kind bug

What this PR does / why we need it:
Fixes the wrong default values of cri_socket that was setting 4 / instead of 3 /
We need this PR because kubelet is throwing errors with the default configuration as described below:

Oct 17 13:58:56 kube-test-sandbox-node-002 kubelet[2401900]: I1017 13:58:56.831825 2401900 remote_runtime.go:71] "Connecting to runtime service" endpoint="unix:////var/run/containerd/containerd.sock"
Oct 17 13:58:56 kube-test-sandbox-node-002 kubelet[2401900]: I1017 13:58:56.831876 2401900 clientconn.go:252] "[core] parsed scheme: \"\"\n"
Oct 17 13:58:56 kube-test-sandbox-node-002 kubelet[2401900]: I1017 13:58:56.831890 2401900 clientconn.go:258] "[core] scheme \"\" not registered, fallback to default scheme\n"

It also puts misleading annotations on nodes:

kubeadm.alpha.kubernetes.io/cri-socket: unix:////var/run/containerd/containerd.sock

Does this PR introduce a user-facing change?:

Fix wrong cri_socket path for containerd

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: maxime1907 / name: Maxime Leroy (dc9d272)

[k8s-ci-robot]

Hi @maxime1907. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[yankay]

/lgtm

Thanks @maxime1907

[liupeng0518]

/ok-to-test

[floryut]

Indeed https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/#general-usage

@maxime1907 Thank you 👍
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, maxime1907

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

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