need to adapt cluster-maxunavailable controller for CAPI 1.12
in https://gitlab.com/sylva-projects/sylva-core/-/jobs/13338295860 (for !5900), we see a failure which is due to the cluster-maxunavailable controller not being able to determine that all CP Machines are up to date this is because the KubeadmControlPlane status has changed for CAPI 1.12: ```yaml status: #... observedGeneration: 2 readyReplicas: 3 replicas: 3 selector: cluster.x-k8s.io/cluster-name=mgmt-2361413971-kubeadm-capm3-virt,cluster.x-k8s.io/control-plane upToDateReplicas: 3 version: v1.34.3 ``` The cluster-maxunavailable tries to use `updatedReplicas` while the new field is `upToDateReplicas`.
issue