1] Proposed title of this feature request

-> Allow Operator Upgrade to a Specific Version Within a Chosen Channel Instead of Only the Latest in OpenShift GUI (OperatorHub)

2] What is the nature and description of the request?

-> Allow Operator Upgrade to a Specific Version Within a Chosen Channel Instead of Only the Latest in OpenShift.

Let's say we have logging-5.9,logging-6.0,logging-6.1 available to install  and I installed 5.9 logging with 5.9.8 version although the latest version in this channel is 5.9.13 so tomorrow if i wish to upgrade to 5.9.9, how is that possible because subscription will point to latest version and install plan will be generated for 5.9.13 only.

3] Why does the customer need this? (List the business requirements here)

> They have around 15+ clusters running OCP & upgrade process of OCP goes from LAB>NPROD->PROD so there is always a gap between 2 environments and even between 2 clusters of same env. And during that gap, new versions of specific operators gets released and since it always points to latest tip/head of specific channel so for example, if lab is on gitops-1.8.5 and 1.8.10 is released at the time of next cluster upgrade, then nprod will move to latest version and so the prod but that's not a good approach since that version is not tested on lab cluster at first place so we should have an option to select specific version of specific channel during operator upgrade

4] List any affected packages or components.

-> OLM