Description

This new content is behind a capability and should only be displayed if the user has this capability. 

Acceptance criteria

Utilize existing Capacity Reservation ID for a new or existing ROSA HCP Machine Pools.

All Capacity Reservation code should be behind a feature flag!

Cluster Details - Machine Pool tab

Updates to "Add HCP Machine Pool" modal

Add Capacity Reservation Preference and ID fields. 

Add the 'Reservation Preference' field to the Overview tab:

      Capacity Reservation
          Reservation Preference: [None | Open | CR only |v]  //  dropdown. 'None' is default
          Reservation Id: [cr-....]                                               //  only enabled when 'CR only'

• Note: CR section & ID field should've been added via https://issues.redhat.com/browse/OCMUI-3832
• If cluster version selected is < 4.19 then disable Capacity Reservation fields and show disabled tooltip as to why disabled and how to enable ("Select cluster version >= 4.19")
• Capacity Reservation Preference values:
  • None = "under no circumstances should this Machine Pool use Capacity Reservation" (defined by AWS)
  • Open = "can use open Capacity Reservation" . 
  • CR only = 'Targeted' === 'cr only' === byCRid.
• Support for autoscaling is underway by Patrick Jennings-- he has an MR up for it today (need vpn) (11/24)

updates to "Edit HCP Machine Pool" modal

• Capacity Reservation preference/id cannot be added/set/edited on an existing machine/node pool.
• The CR fields should not be shown on the Edit HCP Machine Pool modal.

Machine pools table 

1. In the HCP Machine Pool tab, for a machine pool, show in expanded row:
   Capacity Reservation
      Reservation Preference: Open | CR only | None
      Reservation Id: CR-AGEABH35TG
2. Note: CR section & ID field should've been added via https://issues.redhat.com/browse/OCMUI-3832
3. Upgrading of machine/node pools has been merged and is supported in prod already
4. In the event that a user creates a machine pool with the cli and enters a capacity reservation id, but skips the preference value selection, the expanded row should show CR only as the Reservation Preference value
5. The reservation id field should show only if the capacity preference selected is CR only. A value for the reservation id field is not required.

 Additional Resources:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-reservations-create.html

Out of scope

• Support for ROSA Classic, OSD on AWS.
• Use Capacity Reservation during cluster creation (on day-1 machine pool)
  • Customer is responsible for ensuring to create clusters in the region where Capacity Blocks are supported
• Once a machine pool is set to Capacity Reservation, once cannot (at this time) remove the capacity reservation.  DDR indicates one must delete and recreate the MP w/o Capacity Reservation.