Define UX and failures for HC with multi-arch NodePools.

User Story:

Using a multi-arch Node requires the HC to be multi arch as well. This is an good to recipe to let users shoot on their foot. We need to automate the required input via CLI to multi-arch NodePool to work, e.g. on HC creation enabling a multi-arch flag which sets the right release image

Acceptance Criteria:

• Upstream documentation
• HyperShift CLI accomplishes design specified in the document in the Engineering Details section
• HCP CLI accomplishes design specified in the document in the Engineering Details section

Out of Scope:

• See Define UX & failures for HC w/ multi-arch NodePools

Engineering Details:

• See Define UX & failures for HC w/ multi-arch NodePools