[E2E] Update k8s version for EKS so we aren't using an extended support version

[richardcase]

/kind bug

What steps did you take and what happened:

We are currently creating EKS clusters of version v1.24 in our e2e tests. This version went into extended support as of 31st Jan 2024 and therefore each cluster has a "extended support" fee charged.

What did you expect to happen:

That we don't incurr any unecessary costs.

Anything else you would like to add:

Details of the dates for the versions: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html

Environment:

• Cluster-api-provider-aws version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[richardcase]

/triage accepted
/help
/priority critical-urgent

[k8s-ci-robot]

@richardcase:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/triage accepted
/help
/priority critical-urgent

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[richardcase]

/milestone v2.4.0

[richardcase]

(or v2.4.1 as long as it gets on main)