UPSTREAM: <carry>: Define the suggested namespace for NMState CR

knmstate can be realistically installed only in a single instance on the
cluster. Currently, when creating an NMState CR, user is asked to define
the namespace. We can make this easier for them by pre-populating the
namespace to our default - openshift-nmstate.

Signed-off-by: Petr Horáček <phoracek@redhat.com>
(cherry picked from commit 0709939)
(cherry picked from commit 38b3cec)
(cherry picked from commit 5b1375a)
(cherry picked from commit b578607)
(cherry picked from commit 95b57ac)
(cherry picked from commit 62c2026)
(cherry picked from commit 3ff03e2)
(cherry picked from commit b15613f)
(cherry picked from commit ac66f53)
Signed-off-by: Douglas Schilling Landgraf <dougsland@redhat.com>
(cherry picked from commit 60abbb2)
Signed-off-by: Douglas Schilling Landgraf <dougsland@redhat.com>

manifests/4.9/kubernetes-nmstate-operator.v4.9.0.clusterserviceversion.yaml

@@ -15,6 +15,7 @@ metadata:
           }
         }
       }]
+    operatorframework.io/suggested-namespace: openshift-nmstate
     capabilities: Basic Install
     certified: "false"
     categories: OpenShift Optional