DoD:

Since we added support in CAPI upstream for in place propagation of fields and machine -> Node label sync [1], [2], [3], we need to accommodate downstream UX/controllers to play well with the new controller behaviour that will come with the new OCP payloads.

During this work let's make sure we revisit https://issues.redhat.com/browse/HOSTEDCP-262 and make sure we are align with Will and Derek for expected behaviour.

As we transition in to the new capi controllers we need to ensure hypershift behaviour is consistent regardless of the ocp/capi versions running underneath

[1]https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20221003-In-place-propagation-of-Kubernetes-objects-only-changes.md

[2]https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20220927-label-sync-between-machine-and-nodes.md

[3]https://cluster-api.sigs.k8s.io/developer/architecture/controllers/machine-deployment.html#in-place-propagation