Story: As an OpenShift administrators I want to download and start using the Quay AiO installer with as little pre-requisite steps as possible so that I can continue to concentrate on my actual task: installing OpenShift

Background: Depending on the implementation of the installer a user might need to fulfill certain pre-requisites, e.g. install execution(like ansible) or runtime environments (like podman). On top of that invoking the installer might bring some unwanted UX quirks that are specific to the installer technology and not to Quay (e.g. dealing with SSH credentials or Inventory files in Ansible).

Acceptance criteria:

• the installer can be obtained by downloading a single file from the OpenShift mirror (https://mirror.openshift.com/pub/openshift-v4/)
• the installer can be obtained from the Red Hat Cloud Console's download page (https://console.redhat.com/openshift/downloads#tool-x86_64-openshift-install)
• the installer supports switches that are only related to quay, not to the execution or runtime environment of the installer
• the installer should ideally directly executable
• the installer should at most have a single pre-requisite step to be fulfilled before it can be run

Implementation ideas:

1. Wrap an Ansible project in a container (insulate from host requirements and ansible installation)
2. Wrap containerized Ansible in Go (make the installer executable and hide Ansible'isms)
3. Wrap Ansible project in Python using Ansible's Python API and containerize that
4. Wrap Ansible project in C via Ansible's Python API
5. Wrap Ansible project via ansible-runner and containerize that