Phased Rollout for Support of Module Versions

[c-pius]

Context

Side quest from: #1681

ModuleTemplates are changed to define concrete versions of a module. In a first phase, this is will allow users to manually install modules of a given version. KLM shall only support this at a later point in time when follow-up questions are clarified (e.g., what happens if a fixed version installed via KLM runs out of support). A consequence is, that ModuleTemplates are already updated to define concrete versions of a module, while KLM shall still only support installation of modules from a given channel.

KLM has already been prepared to support ModuleTemplates with fixed versions. We want to sustain this implementation (merge it to main), but still prevent the user from choosing fixed module versions in KymaCR.

Questions to be clarified:

1. how can this be moved forward, i.e. rollback the API change, but keep the implementation?
   • without the API change, the implementation will break as it relies on new field in the API

Goals: align on above questions so we can feed this back to #1681

Decision

To be proposed

Consequence

To be proposed