CloudProviderEnabled feature in CAPM3 broke dev-env tests

[tuminoid]

We merged metal3-io/cluster-api-provider-metal3#2108 yesterday, and it seems we have conflicting values in dev-env now.

fatal: [localhost]: FAILED! => {"changed": false, "cmd": "kubectl apply -f \"/home/metal3ci/tested_repo/tests/roles/run_tests/files/manifests/v1beta1_cluster_centos.yaml\" -n \"metal3\"", "delta": "0:00:00.256850", "end": "2025-01-23 22:59:05.092458", "msg": "non-zero return code", "rc": 1, "start": "2025-01-23 22:59:04.835608", "stderr": "The Metal3Cluster \"test1\" is invalid: spec.cloudProviderEnabled: Invalid value: true: cloudProviderEnabled conflicts the value of noCloudProvider", "stderr_lines": ["The Metal3Cluster \"test1\" is invalid: spec.cloudProviderEnabled: Invalid value: true: cloudProviderEnabled conflicts the value of noCloudProvider"], "stdout": "cluster.cluster.x-k8s.io/test1 created\nippool.ipam.metal3.io/provisioning-pool created\nippool.ipam.metal3.io/externalv4-pool created", "stdout_lines": ["cluster.cluster.x-k8s.io/test1 created", "ippool.ipam.metal3.io/provisioning-pool created", "ippool.ipam.metal3.io/externalv4-pool created"]}

/kind bug
/triage accepted
/assign @adilGhaffarDev