[Upstream] CAPI provider for ROSA with HCP - Phase 2 (MVP-2)

Feature Overview (aka. Goal Summary)  

Enable Service Consumer personas to lifecycle managed OpenShift (ROSA with Hosted Control Planes) via CAPI.

Goal

Infuse upstream CAPI with ROSA+HCP Support. Add BYO-OIDC , AWS tags, and Security group to Machinepools support via CAPI.

Target: April 24th

========
Considerations

Once ROSACluster CRD is implemented  in upstream to manage ROSA clusters, downstream bits are to be implemented to integrate with OpenShift/ROSA.

ROSA managed by Capi =  ROSA -> ocm api ->  hypershift api ->  capi -> nodes
the ROSA CAPI Provider will speak to the OCM API via github.com/openshift-online/ocm-sdk-go.  The ROSA CLI cannot communicate to OCM via CAPI directly because OCM does not expose a Kubernetes CAPI Server (that would not scale).  Instead, the user is expected to run a Kubernetes CAPI environment in their computing environment from which they wish to reconcile.

The initial request from the customer was to use CAPI as their authoritative source of truth for all their cluster fleet.This feature covers other bits like modify machinepools, auth-provider etc.

Acceptance criteria.  

• As a Service Consumer, I should use upstream CAPI to provision ROSA+HCP cluster as covered by OCPSTRAT-760
• Following features should be supported by CAPI: 
  • Additional AWS security groups to default machine pools,
  • external BYO identity support,
  • Adding user-tags day-2 support (this is out of scope for demo and will be delivered in Q4)
  • Clusters should support larger worker nodes(250+)