Tracking issue for v1beta3

[richardcase]

/kind refactor
/kind api-change
/priority important-soon
/triage accepted

Describe the solution you'd like

An issue to track the changes that are required in the next API version bump to v1beta3.

Changes:

• Removal of deprecated fields from AWSManagedMachinePool (as a result of the launch template work)
• Make optional API fields consistently pointers (or not pointers) #3243

Anything else you would like to add:

This captures some changes that didn't make it into v1beta2 (v2.0.0) from #2355

### Tasks
- [ ] https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/1166
- [ ] The IamInstanceProfile property on AWSLaunchTemplates should be changed to IAMInstanceProfile (capital IAM) to be consistent with the same property on AWSMachineSpec and Go style guidelines on acronyms.  See: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/3586b3b25153ad525119199dfc9544b69ad0d15f/exp/api/v1beta2/types.go
- [ ] https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/4333
- [ ] Removal of deprecated fields from AWSManagedMachinePool (as a result of the launch template work)
- [ ] https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3243
- [ ] Change the version field on AWSManagedControlPlane, option 1) from @damdo suggestions in #5209

[Ankitasw]

Also #3243

[richardcase]

Also #3243

Added to the list

[AverageMarcus]

The IamInstanceProfile property on AWSLaunchTemplates should be changed to IAMInstanceProfile (capital IAM) to be consistent with the same property on AWSMachineSpec and Go style guidelines on acronyms.

See: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/3586b3b25153ad525119199dfc9544b69ad0d15f/exp/api/v1beta2/types.go

[Ankitasw]

Also #1166

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[richardcase]

/remove-lifecycle stale