User story:

So that I properly ensure that I have my cluster's node pool configured correctly, as a user I want an easy way to find and apply the proper subnet(s).

Acceptance criteria:

• The subnet drop-down will work for public subnets (aka it can be used to select a public subnet)
• The user can select none, one, or many options.
• The list of subnets will be grouped by zones.
• The public subnet drop-down will contain valid subnet IDs based a given region 
• Unit tests, component level testing
• The search on the subnet will be "fuzzy" (approximate string matching) search

Newly added acceptance criteria
The component must support the following validation:

• A user must pick one (and only one) option
• The user must pick at least one but could have multiple selections (aka 1 to many)
• The user can pick 0 or one option (aka 0 to 1)
• The user can pick 0 to many options (aka 0 to many)

More newly added acceptance criteria:

• If the use must pick one and only one option, the drop-down will show the selected subnet and its availability zone.

Additional newly added acceptance criteria:

• The subnet options will be based on the VPC either passed as a prop or saved in the Redux store

See new concise list of criteria  here

Out of Scope

• The subnet drop-down will work for private subnets.  This is being tracked via HAC-2405

Mockups:

Mockups | PD 1434

NOTE: This is a technical story and won't by itself add new functionality.  The drop-down created in this story will be used for HAC-2405, HAC-2979, HAC-3134

------------------------------------------------------------------------------------

Implementation details:

1. Do we have access to backend credentials for Day2 operations for HAC-2979 [Hypershift ROSA][Details] Call node pool endpoint when adding a machine pool for Hypershift clusters.  Can it be used via STS?

Summary:

This will be used on the Hypershift control plane variant of the ROSA wizard for selecting a private or public subnet.