Automation to add the 'spec.replaces' annotation

[pjuarezd]

This allows to have an update graph in Openshift Marketplace Operator updates.

During release we will query the readhat catalog API to get the latest published Operator and set that version as the one to be replaced.

With this no more manual intervention to set the version we are replacing

Example output:

RELEASE=5.0.8 ./olm.sh
operator-sdk version: "v1.22.2", commit: "da3346113a8a75e11225f586482934000504a60f", kubernetes version: "1.24.1", go version: "go1.18.4", GOOS: "darwin", GOARCH: "arm64"
minioVersionInExample: quay.io/minio/minio:RELEASE.2023-07-21T21-12-44Z
minioVersionDigest: quay.io/minio/minio@sha256:8e5e9490cd50018457d53a447e9881eaef6a327b320991347c2ea01db5f3c784
 
certified-operators
package: minio-operator
Generating bundle manifests
WARN[0000] ClusterServiceVersion validation: [OperationFailed] provided API should have an example annotation 
pinning image versions to digests instead of tags
...
To provide replacement for upgrading Operator...
replaces: minio-operator.v5.0.7
clean released annotations
clean root level annotations.yaml

example bundles/certified-operators/5.0.8/manifests/minio-operator.clusterserviceversion.yaml

piVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
metadata:
  annotations:
    name: minio-operator.v5.0.8
...
  version: 5.0.8
  replaces: minio-operator.v5.0.7

example bundles/redhat-marketplace/5.0.8/manifests/minio-operator-rhmp.clusterserviceversion.yaml

piVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
metadata:
  annotations:
    name: minio-operator-rhmp.v5.0.8
...
  version: 5.0.8
  replaces: minio-operator.v5.0.7

[pjuarezd]

closes #1309

[shtripat]

lgtm