Fix login tests for kubeadm-capm3-virt
What does this MR do and why?
In capm3-virt context, kubeconfig provided by rancher contains invalid certificates because rancher API is accessed through bootstrap cluster's ingress proxy (which expose different certificat actually). So in CI we are patching kubeconfig to add insecure option. However this patch was only done for rke2-capm3-virt and not kubeadm-capm3-virt.
Related reference(s)
Fixes #1342 (closed)
Edited by Médéric de Verdilhac