Red Hat OpenShift Service on AWS (ROSA) architectures are being renamed.

The previous 'Rosa classic' architecture will be named:

• "Red Hat OpenShift Service on AWS (classic architecture)".

The newer Rosa architecture with hosted control planes will be called:

• "Red Hat OpenShift Service on AWS".

Acceptance Criteria:

In the scope of this ticket we should make the following text changes:

1. Update the Rosa Getting Started page
   • In the "Complete AWS prerequisites" section, there is a bullet "Set up a VPC for ROSA HCP clusters (optional for ROSA classic clusters)"; we probably want to change to "...(optional for ROSA classic architecture clusters)"

1. Update the 1st step of the Rosa Wizard with new terms.
   • Use of ROSA:
     After we use the full name in the first occurrence and specify the acronym along with it we can use ROSA as seen in the wizard screen - 'Red Hat OpenShift Service on AWS (ROSA)'
   • Since we are defining the architectures also for the first time in the wizard, the titles can specify the full name and acronym.

1. 1. 1. Instead of "Select an AWS control plane type", we should use: "Select the ROSA architecture based on your control plane requirements"

1. 1. 1. The two rosa architecture 'cards' can specify acronym first and then description to make it more readable:
         • Title:  ROSA classic architecture
           Description:  The Red Hat OpenShift Service on AWS (classic architecture) runs an OpenShift cluster with a coupled control and data plane, hosted on dedicated nodes with a shared network.......
         • Title: ROSA hosted architecture
           Description - The Red Hat OpenShift Service on AWS with hosted control planes architecture (ROSA HCP) runs an OpenShift cluster with a decoupled control plane as a multi-tenant workload and a data plane on a separate network for segmented management and workload traffic.....

1.  
2. Update Cluster details -> Overview tab
   • Update "Control Plane type" values to "Hosted architecture" and "Classic architecture"