Installing OpenShift Virtualization collides with existing NMState operator on OCP 4

Issue

• NodeNetworkConfigurationPolicy is not applied to nodes after installing OpenShift Virtualization Operator in a cluster with a standalone NMState Operator installed.

• The nmstate-handler pods in the openshift-cnv namespace do not launch succesfully:

  $ oc get pods -n openshift-cnv -lname=nmstate-handler                                                                                                                                  
  NAME                    READY   STATUS    RESTARTS   AGE
  nmstate-handler-4tjq9   0/1     Running   0          86m
  nmstate-handler-5lfw5   0/1     Running   0          86m
  nmstate-handler-f8whn   0/1     Running   0          86m
  nmstate-handler-hcwjv   0/1     Running   0          86m
  nmstate-handler-ldqlk   0/1     Running   0          86m
  nmstate-handler-wtr6l   0/1     Running   0          86m
  

• nmstate-handler pods in the openshift-nmstate namespace are forbidden to watch resources:

  E1209 14:22:32.602496       1 reflector.go:138] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:229: Failed to watch *v1beta1.NodeNetworkState: failed to list *v1beta1.NodeNetworkState: nodenetworkstates.nmstate.io is forbidden: User "system:serviceaccount:openshift-nmstate:nmstate-handler" cannot list resource "nodenetworkstates" in API group "nmstate.io" at the cluster scope