CAPI v1beta2 phase 1 (new fields & deprecations): OpenStackMachine: update API contract to support Conditions

[EmilienM]

/kind feature

Describe the solution you'd like

TO-DO:

• Deprecate status.ready
• Deprecate status.failureReason and status.failureMessage.
• InfrastructureMachine's status.initialization.provisioned will surface into Machine's status.initialization.infrastructureProvisioned field.
• InfrastructureMachine's status.initialization.provisioned must signal the completion of the initial provisioning of the machine infrastructure. The value of this field should never be updated after provisioning is completed, and Cluster API will ignore any changes to it.
• InfrastructureMachine's status.conditions[Ready] will surface into Machine's status.conditions[InfrastructureReady] condition.
• InfrastructureMachine's status.conditions[Ready] must surface issues during the entire lifecycle of the Machine (both during initial InfrastructureMachine provisioning and after the initial provisioning is completed).

Source

[EmilienM]

I feel like this effort can wait a little. I haven't seen other providers working on it very actively (even CAPV which is usually in advance). Although we might want to work on our terminal failures & conditions.