Add ClusterClass support machine pools

[richardcase]

/kind feature
/priority important-soon
/triage accepted

Describe the solution you'd like

Now the MachinePool support for ClusterClass has merged upstream in CAPI we can add it to CAPA.

There isn't a huge number of docs on this. It's mainly creating new API types:

• AWSMachinePoolTemplate
• AWSManagedMachinePoolTemplate - but there is no point in doing this until AWSManagedCluster and AWSManagedControlPlane have templates (see Add AWSManagedControlPlaneTemplate type #3166)

Anything else you would like to add:

Some prior art:

• ✨ Add MachinePool workers support in ClusterClass cluster-api#9016
• Add ClusterClass Support for Managed Clusters cluster-api-provider-azure#4155

Environment:

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

[richardcase]

/assign
/lifecycle active

[richardcase]

Will do this at the same time as #3166

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[richardcase]

/triage accepted

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[joshfrench]

🙏🏻

[richardcase]

/triage accepte

[k8s-ci-robot]

@richardcase: The label(s) triage/accepte cannot be applied, because the repository doesn't have them.

In response to this:

/triage accepte

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-sigs/prow repository.

[richardcase]

We need to get this done. I've been away for a while but will pick this up again.

/triage accepted

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[richardcase]

/unassign
/help

[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:

/unassign
/help

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-sigs/prow repository.

[aniruddha2000]

/assign

@richardcase I would like to take this up

[richardcase]

/triage accepted

[richardcase]

@aniruddha2000 - I slightly updated the description.