✨ ROSA machinePools support

[muraee]

/kind feature

supersedes #4686

What this PR does / why we need it:

Add initial support for ROSAMachinePools

What this PR does / why we need it:
This PR introduces basic support to create/delete ROSAMachinePoolsand a new cluster template to work with ROSAMachinePools.

It also add several improvements and fixes to the rosa control plane to get cluster creation functional:

• Add ROSAControlPlaneReadyCondition
• Introduce rosaClient helper to communicate with ocm API
• Add WorkerRoleARN field to the API to satisfy latest ocm API requirements
• Add RosaClusterName field to the API to satisfy ocm API requirements for cluster names
• Read credentials(token) from a referenced secret, e.g.:

   apiVersion: controlplane.cluster.x-k8s.io/v1beta2
   kind: ROSAControlPlane
   metadata:
     name: "capi-rosa-quickstart-control-plane"
   spec:
     credentialsSecretRef:
       nmae: rosa-creds-secret
   ...

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):

Fixes #4429, #4460

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• includes emojis
• adds unit tests
• adds or updates e2e tests

Release note:

Introduce basic support for ROSAMachinePools

[k8s-ci-robot]

Hi @muraee. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[muraee]

cc @vincepri this is the updated PR for machinePools

[vincepri]

/ok-to-test

[muraee]

/retest-required

[muraee]

/retest-required

[Ankitasw]

@muraee looks like unit tests are failing, could you fix it?

[muraee]

@Ankitasw fixed! I was chasing down this error since yesterday. seems like one of the new packages we import is initializing klog somewhere and then we end up with a panic: flag x is redefined.
The fix is to reset commandLine flagSet before initializing klog in the test environment.

cc @vincepri

[k8s-ci-robot]

@muraee: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-aws-apidiff-main	d6ad1bc3859c15d612c64628b135daa5c75fd3a2	link	false	/test pull-cluster-api-provider-aws-apidiff-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[vincepri]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vincepri

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vincepri]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment