Ability to declare Operator versions through GitOps/ZTP workflow

1. Proposed title of this feature request
Ability to declare Operator versions through GitOps/ZTP worflow

2. What is the nature and description of the request?
When using the GitOps/ZTP workflow, we need the ability to declare the version of each Operator which is deployed on the managed cluster.
This is currently only possible by creating a custom catalogue for each version of the configuration outside of the GitOps process.
With this enhancement, it will be possible to specify directly in the git repository which Operator versions are applicable to a specific version of a configuration.
This GitOps process should be able to reconcile the Operator versions both during initial deployment as well as when updating the configuration version on a managed cluster.

3. Why does the customer need this? (List the business requirements here)
Our customers typically follow a workflow where a version of a configuration, including specific versions of all software components such as Operators, is defined.
This version of the configuration is then tested in a pre-production environment before being graduated to production.
For this workflow to work, it must be possible to declare the versions of all Operators which are part of a particular version of a configuration.