Add conditions to MachineDeployment Object

[Arvinderpal]

User Story
As a developer/user/operator I would like to have conditions documenting the operational state of MachineDeployment objects.

Anything else you would like to add:
As required by the condition CAEP, the MachineDeployment objects should also provide a Ready condition describing the overall state of the object.

Tasks:

• Summary ReadyCondition and Node availability condition AvailableCondition ✨ Adds AvailableCondition and ReadyCondition Conditions to MachineDeployment #4625
• MachineSet related conditions: MachinesCreatedCondition, MachinesReadyCondition and ResizedCondition ✨ Add Conditions to MachineSet for Machine Create and Ready #5056
• MachineDeployment scaling related conditions: MachinesSpecUpToDateCondition and ResizedCondition
• Remove the use of Phases
• Cleanup: Change calculateStatus() --> updateStatus() to be consistent with the rest of the code base.

Related: Conditions for KCP

/kind feature

[Arvinderpal]

Ideally, we would have something similar to DeploymentProgressing.

This is more to bring in line with how kubectl rollout status works. With clusterctl rollout status my-md-0 we would also watch the progression of the MD by looking at MachinesReadyCondition. I think that would accomplish something similar.

[Arvinderpal]

/cc @fabriziopandini

[vincepri]

/milestone v0.4.0

[vincepri]

/milestone v0.4.0

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[detiber]

/remove-lifecycle stale

[Arvinderpal]

Can I be assigned this ticket? Not that anyone else is jumping to work on it 😆
I'll need this for the clusterctl rollout status command: #3439

[vincepri]

@Arvinderpal Sure, feel free to take it!

/priority important-soon
/assign @Arvinderpal