Allow pulling module templates from custom sources

[kwiatekus]

Description

Currently CLI allows users to pull individual module templates from one and only upstream source.

In order to unify the experience with UI we should extend the possibilities:

• Allow users to pull module templates from various "upstreams", other than the default community module catalog
• Allow users to pull all templates from an upstream source (YAML URL)
• Allow users to upgrade cluster local module templates from the "upstream" (all or individual, named ones)

Reasons

Unify the experience around module discovery with whats design already for Kyma Dashboard

Attachments

[kwiatekus]

this would mean preserving the existing options:
kyma module pull registry-proxy [--version] [--namespace]

..but extended with passing the source URL and all option, i.e
kyma module pull registry-proxy [--namespace foo] [--origin url] [--force] - origin defaults to community
kyma module pull [--namespace foo] [--origin url] [--force] - this command will pull all modules

@pbochynski @mrCherry97 @vicslavova What do you think ?

Summary:

• kyma module catalog [--origin]- origin flag can be: kyma, community, cluster or specified url. defaults to kyma,cluster (list of arguments)
• community is an alias for https://kyma-project.github.io/community-modules/all-modules.yaml - describe it in example
• when --force flag is missing and there is the same community module already installed (same or different version) we should prompt for confirmation
• get rid of --version flag from pull command completely: pull <module name>[@module-version] - support for multiple modules

catalog example usages:

• kyma module catalog - lists managed modules + community modules installed on the cluster
• kyma module catalog --origin kyma --origin community --origin http://google.com - lists managed modules, community modules from the kyma repository and from the provided URL

pull example usages:

• kyma module pull --namespace my-namespace - pulls all community modules from the official kyma repo (https://kyma-project.github.io/community-modules/all-modules.yaml to the my-namespace namespace.
• kyma module pull docker-registry --origin https://remote-repository.com/custom-modules.json - pulls the latest version of docker-registry from custom URL
• kyma module pull docker-registry:0.15.0 --origin community - pulls the specified version from the kyma repository
• kyma module pull chaczapuri-module:0.6.8,pizza-sauce:2.0.25,kentucky-fied-chicken:24.0.1952 --origin https://mammia-mia.com/super-modules.yaml,https://kickapoo.com/space-modules.json

[mrCherry97]

We are allowing for the user to pass his own URL and pull the ModuleTemplates from his own repository, so in my opinion sounds good.

[kwiatekus]

Would you also consider to change the button label to "PULL" ? I know its not a door, or sth, but there is at least for me similarity to "pulling" images via docker CLI or pulling latest code from github.. hence we came for it in CLI. I believe it would also fit here