what

as a user creating ROSA/HyperShift clusters, i want to avoid having redundant resources on my AWS account, which might lead to expended quotas or garbage pileup.

specifically, when prompted to create account-roles via the ROSA CLI, the suggested command should only create the roles necessary for a hosted control-plane cluster AND also create/associate with 'managed policies'.

currently

update to:

For Hypershift clusters, this needs to be updated to the following:

rosa create account-roles

(`--hosted-cp` not need after this merge)
I also think we need to update the 'no roles found' text for Hypershift clusters alert.

Verbiage along the lines of "Rosa Hosted clusters require account-roles which support managed policies...."

For Rosa classic, the cli instructions should be:

rosa create account-roles --managed-policies

Since we want user to create the 'preffered' ARNs with managed policies.  Users can still creare account-roles, unmanaged, simply by not using the --managed-policies flag. 

• The `--managed-policies` parameter is behind a orgId feature flag, may have to add OCM UI to approved list in order to see/use these 'managed policy' propety.

cc @tle