To avoid confusion between OpenShift Service Mesh operators, we should add a "2" to the current "OpenShift Service Mesh" operator displays name(s). Otherwise, for new users, it might not be clear which OSSM operator they should be using.

I am not sure the full implications of this. I will check with CEE/Support to understand the impacts this will have to other automation that keys off of the operator name.

Based on the contents of this file: https://github.com/maistra/istio-operator/blob/maistra-2.6/build/generate-manifests.sh#L42

•  DISPLAY_NAME="Red Hat OpenShift Service Mesh 2"
• CSV_DESCRIPTION="The OpenShift Service Mesh 2 Operator enables you to install, configure, and manage an instance of Red Hat OpenShift Service Mesh 2.6 and earlier releases. OpenShift Service Mesh is based on the open source Istio project."
• APP_DESCRIPTION="Red Hat OpenShift Service Mesh 2 is a platform that provides behavioral insight and operational control over a service mesh, providing a uniform way to connect, secure, and monitor microservice applications."