Description of problem:
Until CNv 4.10, knmstate was installed as part of CNV.
Starting from CNV 4.11, knmstate is installed as a standalone operator, and CNV does not depend on knmstate anymore (unless user explicitly wish to install and use knmstate).
Upgrading CNV 4.10->4.11 should be blocked if knmstate is currently used (i.e. if there are NodeNetworkConfigurationPolicy's applied), and standalone knmstate is not yet installed. Currently - the upgrade is blocked even if there is no policy applied.

Version-Release number of selected component (if applicable):
OCP 4.11.0
CNV 4.10.5
knmstate v4.10.5-1
HCO v4.10.5-1
cluster-network-addons-operator v4.10.5-1

How reproducible:
100%

Steps to Reproduce:
1.
On a cluster with OCP 4.11 and CNV 4.10.z (z>=2) - make sure there is no NodeNetworkConfigurationPolicy (NNCP):
$ oc get nncp
No resources found

2.
Make sure standalone knmstate is not installed:
$ oc get ns | grep nmstate
$

3.
Check the Upgradeable status of HCO:
$ oc get hco -n openshift-cnv kubevirt-hyperconverged -ojsonpath=

| jq
[
...

]

<BUG>
Upgradeable should be "True"