WIP: Add v1beta2 contract fields (initialization, conditions) to API types

[willie-yao]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
This PR adds the v1beta2 CAPI contract fields to all CAPZ provider API types (Stage 1 of the conditions migration). This is purely additive with no behavioral changes. Controllers will dual-write these fields in a follow-up PR.

General implementation formula:

• Types with Ready → need an Initialization struct
• Types with Conditions → need a v1beta2 substruct + getter/setter methods
• Types with FailureReason/FailureMessage → need deprecation comments
• ControlPlane types → use ControlPlaneInitialized instead of Provisioned

Changes per type:

• Add status.initialization.provisioned *bool to all InfraCluster/InfraMachine types (AzureCluster, AzureMachine, AzureManagedCluster, AzureManagedMachinePool, AzureMachinePool, AzureMachinePoolMachine, and ASO-managed types)
• Add status.initialization.controlPlaneInitialized *bool to ControlPlane types (AzureManagedControlPlane, AzureASOManagedControlPlane)
• Add status.v1beta2.conditions []metav1.Condition with GetV1Beta2Conditions/SetV1Beta2Conditions methods to all types that have conditions
• Add deprecation comments to status.ready, failureReason/failureMessage, errorReason/errorMessage

These fields are not yet read by CAPI. That only happens when the CRD label is updated to declare v1beta2 contract compliance in a later PR.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes part of #6136

Special notes for your reviewer:

Contract documentation pages

• InfraCluster contract (v1beta2)
• InfraMachine contract (v1beta2)
• ControlPlane contract (v1beta2)

TODOs:

• squashed commits
• includes documentation
• adds unit tests
• cherry-pick candidate

Release note:

Add v1beta2 contract fields (initialization, conditions) to API types

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mboersma for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[codecov]

Codecov Report

❌ Patch coverage is 1.53846% with 64 lines in your changes missing coverage. Please review.
✅ Project coverage is 43.57%. Comparing base (4c5753c) to head (f5111c0).
⚠️ Report is 7 commits behind head on main.

Files with missing lines	Patch %	Lines
api/v1beta1/azurecluster_types.go	0.00%	8 Missing ⚠️
api/v1beta1/azureclusteridentity_types.go	0.00%	8 Missing ⚠️
api/v1beta1/azuremachine_types.go	0.00%	8 Missing ⚠️
api/v1beta1/azuremanagedcontrolplane_types.go	0.00%	8 Missing ⚠️
api/v1beta1/azuremanagedmachinepool_types.go	0.00%	8 Missing ⚠️
exp/api/v1beta1/azuremachinepool_types.go	0.00%	8 Missing ⚠️
exp/api/v1beta1/azuremachinepoolmachine_types.go	0.00%	8 Missing ⚠️
azure/scope/machine.go	0.00%	2 Missing ⚠️
azure/scope/machinepool.go	0.00%	2 Missing ⚠️
azure/scope/machinepoolmachine.go	0.00%	2 Missing ⚠️
... and 2 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6199      +/-   ##
==========================================
- Coverage   43.67%   43.57%   -0.10%     
==========================================
  Files         289      289              
  Lines       25495    25551      +56     
==========================================
  Hits        11134    11134              
- Misses      13559    13615      +56     
  Partials      802      802              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[willie-yao]

/retest

[k8s-ci-robot]

@willie-yao: Closed this PR.

Details

In response to this:

/close

Reconsider implementing new api version from the start

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.

[k8s-ci-robot]

@willie-yao: Reopened this PR.

Details

In response to this:

/reopen

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.