Fix baremetal operator replicas setting

What does this MR do and why?

We observed a failure in management cluster upgrade tonight (https://gitlab.com/sylva-projects/sylva-core/-/jobs/6663136006) that was caused by metal3 pod delaying the drain of first CP node:

E0418 21:42:16.478322       1 machine_controller.go:652] "error when evicting pods/\"baremetal-operator-controller-manager-58f877c58d-9f8fb\" -n \"metal3-system\" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.\n" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="sylva-system/mgmt-1259219677-rke2-capm3-virt-control-plane-2hv2f" namespace="sylva-system" name="mgmt-1259219677-rke2-capm3-virt-control-plane-2hv2f" reconcileID="e1ee4ed1-0956-4efc-8617-e2fa7b0cb44d" RKE2ControlPlane="sylva-system/mgmt-1259219677-rke2-capm3-virt-control-plane" Cluster="sylva-system/mgmt-1259219677-rke2-capm3-virt" Node="mgmt-1259219677-rke2-capm3-virt-management-cp-2"

baremetal operator deployment had only one replica as it was not properly configured in the chart, this MR fixes that issue