override/empty target namespace

[Ladanow]

Some operators are not compatible with adding targetNamespace as their own, this is automatically done when we create a new namespace.

for example, performance-addon-operator can't monitor its own namespace.

apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"operators.coreos.com/v1","kind":"OperatorGroup","metadata":{"annotations":{},"labels":{"app.kubernetes.io/instance":"npss-tnc-hub"},"name":"openshift-performance-addon-operator-operator-group","namespace":"openshift-performance-addon-operator"},"spec":{"targetNamespaces":["openshift-performance-addon-operator"]}}

[claudiol]

We might want to add a way to control the parameters that VP uses while creating operatorgroups for operator installation. The framework always creates an OperatorGroup with spec.targetNamespaces and some operators want an OperatorGroup without targetNamespaces. @mbaldessari