User story:

As a user of the Rosa wizard for Hosted/Hypershift clusters, on Step 2 I would like the ARNs with managed policies to be selected by default and mark as preferred.  If I select a ARN with managed policies, then on the following step the OS Version dropdown should not show anything earlier than v 4.11.

Acceptance criteria:

• On Step 2 Accounts and roles (for Rosa Hosted/Hypershift only):
  • Hosted ROSA - filter out non-managed policy ARNs since right now these are these are the only ARNs that will be usable for hypershift
  • Standalone ROSA - Auto-select ARNs with managed policies by default and mark as preferred via a "Recommended" label (see mockup)
    • When ARNs with managed policies selected, update the version info alert to "...is compatable with OpenShift version 4.11 or newer" (see mockup)
• On Step 3 Cluster settings (for Rosa Hosted/Hypershift only)
  • If ARN with managed policies was selected tag any OS version 4.10 or older as 'incompatable with previously selected ARN`.

Mockups:

Mockups | PD-1483

Implementation details

 To get a list of ARN sets associated with the currently selected AWS infrastructure account, the UI uses endpoint

 /aws_inquiries/sts_account_roles

which managed_policies and hcp_policies have been added to this endpoints return response:

Are the two fields different, or will they always report the same value?
Yes - the fields will eventually be different

• For hypershift managed policies both fields are true
• For rosa classic unmanaged both are false
• (out of scope) For rosa classic managed policies (the epic is on hold right now) managedPolicies:true and hcpManagedPolicies:false