Review requirements towards Community Modules

[kwiatekus]

Description
As part of the initial implementation (POC of new kyma CLI) we are using a temporary source of information about community modules. This will change.

• Review Iteratively moving forward with module requirements and aligning responsibilities lifecycle-manager#1681
• identify any potential differences ( comparing to the temporarty json file we have been rellying on so far in the POC phase ).
• align with CLI team and KLM team to identify work on CLI side.
• express any additional requirements comming from CLI end

Reason
CLI command for reading available modules and installing them heavily rely on the community modules API.
In order to move away from POC towards stable solution we need to allign (understand concepts and identify our requirements) with the new API

Attachments
POC issues we have been implementing so far when relying on the temporary json file:
#2083
#2117

[pPrecel]

Together with @kwiatekus and @Cortey we've performed research in the context of potential differences between the actual implementation of usage of temporary JSON file and the desired solution. The final shape of the list with all modules and community modules will be totally different than our actual implementation and even this is described in the linked POC.

Finally, a list of ModuleTemplates will be delivered as the only source of truth. This is really fresh idea so there is no ticket/POC that is describing this idea so we have to wait and block this story until the topic moves on.

[kwiatekus]

@kyma-project/jellyfish Asked to re-review
kyma-project/lifecycle-manager#1681
An ask to verify if the updated ModuleTemplateCR and new ModuleReleaseMetaCR goes in hand with kyma CLI