Ensure stability and feature completeness of MAPO tech preview so that we can make it GA

The requirements for MAPO remain the same:

• Implements the OpenShift Machine Controller
• Defers as much functionality as possible to the upstream CAPO (Cluster API Provider OpenStack) project
• Imports CAPO as a library
• Implements type conversion between Machine API and Cluster API for OpenStack components.

MAPO must at a minimum:

• Have feature parity with OpenShift CAPO
• Have its repository hosted under the openshift organisation on github
• Be part of the OCP release payload
• Have pre-submit jobs CI with functional tests

Part of this work will also consist in pushing the OpenShift CAPO changes to Kubernetes CAPO upstream.