I'd like to check the Golang Memcached Sample publish on OperatorHub io and RedHat Community

Feature Request

Describe the problem you need a feature to resolve.

I'd like to check the Golang Memcached Sample publish on OperatorHub io and RedHat Community so that:

a) I could easily test/check the default example integrated with OLM on k8s/OCP/OKD vendors
b) We could ensure that the default sample attends the minimal requirements to work with OLM properly
c) I could easily check how the common case example provided by SDK works on the cluster

The repos are:

• k8s-operatorhub/community-operators/operators
• redhat-openshift-ecosystem/community-operators-prod/operators

Describe the solution you'd like.

a) For each SDK release we could have a new Memcached Operator sample version published on both repositories (new PR pushed against them)
b) The version of the bundle would be the same as the SDK release

PS.: For we do not need to define/configure the upgrade path using replace/skip/skipRange we need to have the project with the semver mode enabled so that we do not need to do any logic to manage this config and we can make the things simple. It is done in the ci.yaml file:

# Use `replaces-mode` or `semver-mode`. Once you switch to `semver-mode`, there is no easy way back.
updateGraph: replaces-mode

/language go

Start by reviewing the sample's ci.yaml, especially the updateGraph setting, then inspect the contribution and bundle requirements in the k8s-operatorhub/community-operators and redhat-openshift-ecosystem/community-operators-prod repositories. Done means defining the release workflow and producing a versioned Memcached Operator publication PR for both repositories for each SDK release.