[Module catalogue improvements ] Extend Kyma CR module list with an explicit version

Description

Note: This issue is just about API change, the change in the controller logic is expected to be implemented here

In order to support explicit module version, we need to add an optional version attribute to the Kyma CR module list.

An example:

Use case 1 / existing: User wants to enable a specific channel of a module in their cluster.

[...]
- modules:
  - name: my-module
    channel: fast
[...]

Use case 2 / new: User wants to enable a specific version of a module in their cluster.

[...]
- modules:
  - name: my-module
    version: 1.0.0
[...]

Reasons

We need this because users must be given an option to install a specific version of the module. If the user wants to enable a specific module version, a ModuleTemplate CR corresponding to that version must exist in the control-plane.

Acceptance Criteria

[ ] Add new optional version attribute is to the module list in Kyma CR. Must be a semantic version or a defined identifier like regular or fast (see https://github.com/kyma-project/lifecycle-manager/issues/1590).
[ ] Add a validation: either channel or version is present - it is an error to provide both

Feature Testing

e2e test for the validation. Can be done with local EnvTest.

Testing approach

No response

Attachments

No response

Related issue(s)

https://github.com/kyma-project/lifecycle-manager/issues/1590

kyma-project / lifecycle-manager