Review if we still need to install cri-tools form Kubernets 1.31 and forward

[ralgozino]

Starting from Kubernetes 1.31 kubeadm will not depend on cri-tools anymore:

• Make kubeadm independent from crictl kubernetes/kubernetes#124685

[g-iannelli]

Checking the ansible roles, crictl is used in the renewal certificate examples. Maybe it's not required directly in the roles.

The kubeadm deb/rpm packages will continue to install the cri-tools package up to Kubernetes version 1.31.
In kubernetes 1.32 it will be removed.

IMHO this issue should be postponed to KFD 1.32

[ralgozino]

We are using it also in the renew certificates command in the distribution:

https://github.com/sighupio/fury-distribution/blob/main/templates/kubernetes/onpremises/98.cluster-certificates-renewal.yaml.tpl#L80-L81

https://github.com/sighupio/fury-distribution/blob/main/templates/kubernetes/onpremises/98.cluster-certificates-renewal.yaml.tpl#L85

https://github.com/sighupio/fury-distribution/blob/main/templates/kubernetes/onpremises/98.cluster-certificates-renewal.yaml.tpl#L92

https://github.com/sighupio/fury-distribution/blob/main/templates/kubernetes/onpremises/98.cluster-certificates-renewal.yaml.tpl#L99

We'll need to either make sure we keep installing critools in 1.32 or look for an alternative in the renew certificates role.

I think having critools in the nodes for troubleshooting can be handy, but it can be installed when needed too. So if it simplifies our installer, it could be beneficial to drop it.