Version independent OCP installer

1. Proposed title of this feature request

Version independent OCP installer

2. What is the nature and description of the request?
 
Telco Partners will tie particular releases of their product to particular versions of OpenShift. E.g. Partner Release Foo may be tied to OCP 4.10, Partner Release Foo+1 may be tied to OCP 4.12.
 
Telco Partners would like to be able to make use of the latest installer technology when it becomes available even if it comes in a release that they not planning on using or if they are still deploying a previous release for some customers.
 
E.g. Telco Partner Foo has a customer for whom they are deploying Partner Release Foo (based on OCP 4.10) into but OpenShift 4.11 is already GA and the 4.11 installer has a feature/capability that Partner Foo would like to use, so they would like to use the installer from OCP 4.11 to deploy OCP 4.10 based clusters.

3. Why does the customer need this? (List the business requirements here)

• Partner is able to use the latest installer features with latest OCP version while still supporting older OCP versions using the same installer.  Partner can assume support of OCP installer compatible with older version of OCP (N-x releases, where x is to be decided/agreed). This reduces the overhead for the Partner's customer teams as they can always use the same installer version when they have customers who are deployed (or deploying) using different OCP versions.{}{}
• Partner does not need to maintain multiple branches for the OCP installer in the Partner's internal CI and can just maintain the latest version of OCP installer in their CI.{}{}
• OCP installer can be provided to Partner's end customer without any changes from the Partner with full automation ( e.g Ansible playbooks) helping with quick delivery of software .{}{}
• If a system is installed from scratch with Installer version X and the partner needs to perform life cycle management like a scale-out the Partner can do with the latest installer version Y and does not need to maintain multiple installer versions and operating procedures that are dependent on the OCP version the Partner's customer's clusters are using.

4. List any affected packages or components

OCP installer