**What problem does this PR solve?**:
Adds AWS CCM support for Kubernetes v1.29. While testing I also found an
upstream change kubernetes/kubernetes#121028 and
to fix that added `hostNetwork: true` to the CCM pods. Upstream CAPA
templates and the Nutanix CCM already use `hostNetwork: true`, so it
made sense to go with that approach here too.

**Which issue(s) this PR fixes**:
Fixes #

**How Has This Been Tested?**:
<!--
Please describe the tests that you ran to verify your changes.
Provide output from the tests and any manual steps needed to replicate
the tests.
-->
Created an AWS v1.29.4 cluster with the following lookup envs:
```
AMI_LOOKUP_BASEOS=rocky-9.1
AMI_LOOKUP_FORMAT=konvoy-ami-{{.BaseOS}}-release-?{{.K8sVersion}}-*
AMI_LOOKUP_ORG=999867407951
```

**Special notes for your reviewer**:
<!--
Use this to provide any additional information to the reviewers.
This may include:
- Best way to review the PR.
- Where the author wants the most review attention on.
- etc.
-->

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.

In k8s >= 1.29 kubelet no longer sets node internalIP when using external cloud provider
kubernetes/kubernetes#121028

This regresses node startup performance in Azure CNI Overlay and Podsubnet clusters, which require the node to be
assigned an internal IP before configuring pod networking.
To improve node startup performance, explicitly set `--node-ip` to the IP returned from IMDS so kubelet sets
the internal IP when it registers the node.
If this fails, skip setting --node-ip, which is safe because cloud-node-manager will assign it later anyway.