Ship Fusion HCI with OCP and Fusion container images

When installing into an air-gap environment it is expected to mirror a specific OpenShift release and the Fusion images, then import them into the client network and push into the client provided private registry. This process is not tested properly and causes a poor first impression with the client.

For the mirroring we currently do not specify the channels for the OCP packages and pull all which results in over 1TB of images to import! If the client has a process to scan imported software this causes a delay and creates a poor first impression of a 'rapid' installation portrayed by the sales literature.

We should also include OCP operators for standard features that are required to commission a Fusion HCI such as observability, NFD, NVIDIA GPU, logging, cert manager, etc. These are all required to have a working system that the client will approve for production use and should not be ignored in the documentation. See example image set configs for mirroring OCP 4.18.22 and ISF 2.11

1) We should specify every image digest for OCP so that only the required images are mirrored.
2) We should ship the service node with a fully populated mirror-registry (Quay lite from RH) that can be used as a local registry for the installation and these images could also be mirrored to the client private registry for ongoing production use. This would accelerate the installation process and avoid the mirror and importing process completely.