Description of problem:
Cluster-logging-operator couldn't upgrade from 4.3.1 to 4.3.2 due to `olm.skipRange: ‘>=4.2.0 <4.3.0’` in the csv file.

I think it should be ` olm.skipRange: ">=4.2.0 <4.3.2-xxxxxxxx"`

$ cat tempdir/manifests/cluster-logging/4.3/cluster-logging.v4.3.0.clusterserviceversion.yaml 
#! validate-crd: deploy/chart/templates/0000_30_02-clusterserviceversion.crd.yaml
#! parse-kind: ClusterServiceVersion
apiVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
metadata:
  # The version value is substituted by the ART pipeline
  name: clusterlogging.4.3.2-202002122007
  namespace: placeholder
  annotations:
    capabilities: Seamless Upgrades
    categories: "OpenShift Optional, Logging & Tracing"
    certified: "false"
    description: |-
      The Cluster Logging Operator for OKD provides a means for configuring and managing your aggregated logging stack.
    containerImage: image-registry.openshift-image-registry.svc:5000/openshift/ose-cluster-logging-operator:v4.3.2
    createdAt: 2018-08-01T08:00:00Z
    support: AOS Logging
    # The version value is substituted by the ART pipeline
    olm.skipRange: ">=4.2.0 <4.3.0"


Version-Release number of selected component (if applicable):
clusterlogging.4.3.2-202002122007

How reproducible:
Always

Steps to Reproduce:
1. deploy cluster-logging-operator 4.3.1-202002032140 via OLM
2. then try to upgrade it to 4.3.2-202002122007
3.

Actual results:
The operator isn't upgraded, it still 4.3.1

Expected results:


Additional info: