Add channel to compliance-operator policy

If there are multiple catalogs that provide the compliance-operator,
then the OperatorPolicy may give an error while determining the default
channel for the operator. Providing the channel directly prevents this
issue.

Refs:
 - https://issues.redhat.com/browse/ACM-29933

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>

Author: JustinKuli

frontend/src/wizards/Governance/Policy/stable/CA-Security-Assessment-and-Authorization/policy-compliance-operator-install.yaml

@@ -3,7 +3,7 @@
 #
 # If set to "enforce" it'll install the operator.
 #
-# Note that OpenShift 4.6 is required.
+# Note that OpenShift 4.6+ is required.
 apiVersion: policy.open-cluster-management.io/v1
 kind: Policy
 metadata:
@@ -51,6 +51,7 @@ spec:
             namespace: openshift-compliance
             source: redhat-operators
             sourceNamespace: openshift-marketplace
+            channel: stable
             # Conditionally configure a nodeSelector for installing on ROSA hosted control planes
             config: '{{ if and (eq "ROSA" (lookup "cluster.open-cluster-management.io/v1alpha1"
               "ClusterClaim" "" "product.open-cluster-management.io").spec.value) (eq "true"