User Story

As a customer of ROSA/OSD, if the r5-series AWS instance type is not available to me or in my chosen region, instead of the cluster install failure, the installation should defer to the equivalent m5-series (according to SDE-2109) for the infra nodes.

In ROSA CLI, the install workflows should include the ability to pass a parameter such as
`--infra-nodes m5` to replace the default of r5-series with the m5-series. In automatic/default workflow, the detect if r-series is unavailable and auto-select the equivalent m5-series.

For the ROSA UI, the similar changes should apply..

• if r5-series is not available, then just create infra nodes as m5-series equivalent (This should hopefully be backend/API changes only)
• but also offer the in-UI option to select m5 instead of r5 (new UI work needed for this)

For consideration: We will likely need to provide a mapping of equivalents in case SRE decides to resize the infra nodes for a customer, or in case there's a future where m6 and r6 succeed the m5 and r5 series.

Acceptance Criteria

• Customers that do not have access to r5 series should no longer have failed cluster installations and instead get m5 series as an immediate replacement and also have the option to simply specify the alternative.
• This option should be exposed in our API so that Terraform-built clusters have the same capability at install-time.
• This change is for install-time only
• The ROSA CLI and ROSA UI experiences are both updated to accomodate this change before the epic is closed.
• documentation about this change must be captured before this epic is closed.

Default Done Criteria

• All existing/affected SOPs have been updated.
• New SOPs have been written.
• Internal training has been developed and delivered.
• The feature has both unit and end to end tests passing in all test
  pipelines and through upgrades.
• If the feature requires QE involvement, QE has signed off.
• The feature exposes metrics necessary to manage it (VALET/RED).
• The feature has had a security review.* Contract impact assessment.
• Service Definition is updated if needed.* Documentation is complete.
• Product Manager signed off on staging/beta implementation.

Dates

Integration Testing:
Beta:
GA:

Current Status

GREEN | YELLOW | RED
GREEN = On track, minimal risk to target date.
YELLOW = Moderate risk to target date.
RED = High risk to target date, or blocked and need to highlight potential
risk to stakeholders.

References

Links to Gdocs, github, and any other relevant information about this epic.