UPSTREAM: <carry>: Provide default NMState CR

Currently, admins have to install the NMState in two steps.  First they
have to install the operator and then navigate to the operator menu to
create an NMState CR.

With this patch, these two are merged into a single step where while
installing NMState operator, user will be asked to create the CR since
it is required. That then immediatelly triggers deployment of NMState
operands as a part of the NMState operator installation.

Signed-off-by: Petr Horáček <phoracek@redhat.com>
(cherry picked from commit b6dbdf5)
(cherry picked from commit 600c605)
(cherry picked from commit ab635c0)
(cherry picked from commit d395c3d)
(cherry picked from commit f81f823)
(cherry picked from commit 464f992)
(cherry picked from commit 943b62e)
(cherry picked from commit 57ac5d7)
(cherry picked from commit a53320c)
Signed-off-by: Douglas Schilling Landgraf <dougsland@redhat.com>

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

@@ -2,6 +2,20 @@ apiVersion: operators.coreos.com/v1alpha1
 kind: ClusterServiceVersion
 metadata:
   annotations:
+    operatorframework.io/initialization-resource: |-
+      {
+        "apiVersion": "nmstate.io/v1beta1",
+        "kind": "NMState",
+        "metadata": {
+          "name": "nmstate",
+          "namespace":"openshift-nmstate"
+        },
+        "spec": {
+          "nodeSelector": {
+            "beta.kubernetes.io/arch": "amd64"
+          }
+        }
+      }
     alm-examples: |-
       [{
         "apiVersion": "nmstate.io/v1beta1",