What this PR does / why we need it:
kube-vip has issues when being used with k8s 1.29. This PR fixes them by

1. From 1.29, a change has been made to kubeadm to provision a separate Kubeconfig file called super-admin.conf and reducing the admin.conf User's access to the permissions provided by the cluster-admin ClusterRole. It is to be noted that in a multi-cluster setup, the super-admin.conf is only created on the primary control plane node, which runs kubeadm init is failing because kube-vip deployment is hardcoded to use admin.conf but kube-vip requires elevated permissions to access the API server during cluster initialization, which are available only when using the super-admin.conf.
2. From 1.29, hostAliases do not work as expected. Add a work around to mount the volumes to the kube-vip pod manifest.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1792

Special notes for your reviewer:

/area provider/ibmcloud

1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

Update kube-vip spec in cluster templates to adopt k8s 1.29