Release pipeline is creating release branch from `master` and then set the version (for example 0.14.0).

The set version script will take the old version as the one currently on the repo before the change. In that case, it is `1.0.0-snapshot`.

In the end, the script is putting is csv `kogito-operator.v1.0.0-snapshot` instead of `kogito-operator.v0.13.0`.

We need a way to set the correct latest version in csv.

Example PRand discussion: https://github.com/kiegroup/kogito-cloud-operator/pull/524#discussion_r472955907

A solution would be to look into the different versions of `deploy/olm-catalog/kogito-operator` and take either the latest minor if exists (would be 0.13.0 in the example), or latest micro (could be maybe 0.12.1 if 0.13.0 is not yet released). All csv versions should anyway be present into the repository.

Another solution could be to look into `deploy/olm-catalog/kogito-operator/kogito-operator.package.yaml` file ?