🌱 Bump CAPI to v1.9.z

[damdo]

What type of PR is this?
/kind support

What this PR does / why we need it:
CAPI v1.9.z is out now, so this PRs bumps the CAPI version used by CAPA with the new released one.

Bumps CAPI to v1.9.x based on https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/book/src/developer/providers/migrations/v1.8-to-v1.9.md

action required
Bump CAPI to v1.9.z
!! ACTION REQUIRED BEFORE UPGRADING !!
If you are using the AWSManagedControlPlane to provision EKS clusters and you do not have a spec.Version specified in such resource (meaning you are relying on the default that AWS provides), you will need to either:
a) explicitly set such `spec.Version` field before upgrading CAPA
or b) disable the MachineSetPreflightChecks in your cluster either:
b1) by setting this core CAPI feature gate to `false`
b2) or by disabling it via the relevant annotation on all the machineSets belonging to said cluster (follow this guide on how to do this: https://cluster-api.sigs.k8s.io/tasks/experimental-features/machineset-preflight-checks).
This is necessary as core CAPI 1.9 introduces a feature gate change, setting MachineSetPreflightChecks=true, which in turn relies on the presence of spec.Version and status.Version on the AWSManagedControlPlane object.
We are planning a future refactor of these API fields in v1beta3 (https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3853).
Other places where you can find details on this are:
- https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/5225
- https://github.com/kubernetes-sigs/cluster-api/issues/11117
- https://kubernetes.slack.com/archives/CD6U2V71N/p1739783013734149

Fixes #5335

[damdo]

/hold

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks pull-cluster-api-provider-aws-e2e

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks pull-cluster-api-provider-aws-e2e

[damdo]

/retest

[damdo]

We are hitting #5139 with this, as we are now using the 1.30+ k8s version in testing.

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks pull-cluster-api-provider-aws-e2e

[damdo]

/unhold

[richardcase]

@damdo - would you be able to squash your commits?

[damdo]

@richardcase done, I left the 3 most relevant atomic commits there. Squashed the rest.

[damdo]

Also

/assign @nrb

[nrb]

@damdo The top line of the description says this is blocked by an open issue - is that still true?

[damdo]

@nrb not anymore as we moved to use NLBs in testing

[nrb]

/approve

[richardcase]

Looks great @damdo .

Just 1 nit, normally i would say to ignore it but as it will be in the CRD it might be worth correcting. wdyt?

[nrb]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [nrb]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[richardcase]

/lgtm