[Module catalogue improvements] Implement new Module Catalog support

[Tomasz-Smelcerz-SAP]

Description

Implement new logic to support use cases described here
The API changes are introduced by these two issues: #1590, #1589.

Note: At this moment it is not 100% clear which scenarios related to module management must be supported. Precisely, what happens if:

• A Module foo is installed from a channel fast. After a long time, the Module Catalog changes and there is no more ModuleTemplate for foo in the fast channel What happens then?

Such scenarios must be either excluded (it will not happen because...) or implemented as part of this issue.

Reasons

We need it to support use cases described here

Acceptance Criteria

• Resolve doubts related to Module Catalog changes (as described) - this requires a separate issue related to module sunset procedure. We do NOT implement it here.
• The Lifecycle-Manager must support both the old ModuleTemplates and a new ones (with extended attributes) - we must provide a smooth migration path
• Installing an explicit module version is supported (this is new)
• Installing a module using a channel name is supported (this logic already exists)
• Automatic upgrade of a module installed using a channel name is supported (this logic already exists)
• No module downgrade is supported (based on semantic versioning)

Feature Testing

unit test, integration test, e2e test

Testing approach

Ensure in the e2e test that the old ModuleTemplate attributes (as of now) and the new ones (as implemented by this issue) are supported.

Attachments

No response

Related issue(s)

#1472, #1590