Remove the version restrictions on multiple instances of AIOps on a single cluster

The product documentation for AIOps up to 4.13.1 states:

Each new instance of IBM Cloud Pak for AIOpsthat you deploy on the cluster must be the same version or a more recent version than any already‑installed instances on the cluster. Older versions cannot be deployed into a cluster with a pre-existing newer version. This is because custom resource definitions (CRDs) are cluster-scoped resources, and overwriting them with an older version would break the newer version.

And also:

If you deploy multiple instances of IBM Cloud Pak for AIOps on a single cluster, then the difference between the instances can vary by a maximum of one release. This maximum skew must be maintained even during upgrade. When upgrading multiple instances of IBM Cloud Pak for AIOps on a single cluster, you must upgrade the oldest instance first.

Both of these restrictions have proven to cause issues for deployments at customers. They severely limit the utility of having multiple instances and place a considerable burden of administration and maintenance. In addition several common use cases - deployment of an instance for regression testing, or validating a new feature, or running through a specific recovery scenario - are severely impacted by these restrictions. 

It would be beneficial to our customers to provide complete isolation of AIOps instances within OpenShift namespaces such that these restrictions could be lifted, so that instances can be deployed within a cluster without regard to the presence or version of any other instance on that same cluster.