Update CAPI / CAPZ / CAPA controller to support K8s release v1.30.x

[njuettner]

In order to support K8s v1.30.x we must update our fork https://github.com/giantswarm/cluster-api.

Latest Release is currently v1.6.5 from upstream which only supports until v1.29.x Release and this is what we use in CAPZ and CAPA right now.

We would need v1.7.x to support v1.30.x, see https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.7.1

Additionally we would also need to update CAPZ and CAPA controllers to support CAPI v1.7.x (usually they bump dependencies in a minor release)

And we need need to upgrade MC’s to at least v1.26.x
because 1.7.x supports MC's Management Cluster: v1.26.x -> v1.30.x so we need to ensure that as well

TL;DR:

• Upgrade MCs to Kubernetes v1.26.x
• Update CAPI fork (cluster-api repo) and cluster-api-app to v1.7.x
• Update CAPA / CAPZ / CAPVCD / CAPV to whatever version where they start using CAPI v1.7.x as a dependency
• Ideally testing this in a separate installation to see if everything works
• Update capa/capz/capv/capcd/-app-collection
• Fix upstream issues to support Kubernetes v1.30 (e.g. CAPA's ELB health check fails with Kubernetes >=v1.30.x kubernetes-sigs/cluster-api-provider-aws#5139 – might already be okay because we set ciphers explicitly in the cluster chart)