Adopt CAPI v1beta2 conditions

[adilGhaffarDev]

• The fields .status.failureMessage and .status.failureReason are being deprecated in Cluster API (CAPI). Refer to the related PR: #11317.

  • Remove capierrors (sigs.k8s.io/cluster-api/errors) from our implementation.
  • Define a custom error struct to handle similar functionality.
  • Consider completely removing .status.failureMessage and .status.failureReason and add conditions for these failures. Refer to the proposal for detailed information.

• Add API types to support compatibility between v1beta2 and v1beta1 status fields. Relevant PR: #11234

• Contract changes overview:
  • [InfrastructureCluster] (https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20240916-improve-status-in-CAPI-resources.md#infrastructurecluster)
  • [InfrastructureMachine] (https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20240916-improve-status-in-CAPI-resources.md#infrastructuremachine)

• CAPI introduces MachineReadinessGate in MachineSpec. This allows third-party controllers to add conditions.

  • Evaluate the potential use of MachineReadinessGate in the Metal3 (CAPM3) implementation.
  • Consider adding a Metal3MachineReadinessGate if there’s a clear use case.

• The output of kubectl get machines -o wide has been improved. For details, refer to Machine Print Columns.

  • Enhance the kubectl get m3m -o wide output for Metal3 resources to provide similar improvements.

[adilGhaffarDev]

Let's keep updating this as we get more information from the CAPI regarding contract changes.

[Rozzii]

/triage accepted

[Rozzii]

/kind feature