[Kyma Dashboard] Support for the Community Modules

[mrCherry97]

Description
Kyma comes with a set of Kubernetes building blocks (called modules). Modules are independent: can be added and removed in the runtime, and have an independent release cycle. Each module provides and a manager (Kubernetes operator) and a default configuration (custom resource). Some modules are available in the managed SAP Kyma Runtime with full support (SLA, automatic upgrades). Other modules (community modules) are offered only with community support (no SLA, manual upgrades, possible breaking changes). In the managed clusters the Kyma Lifecycle Manager (KLM) is responsible for installation and automatic upgrades of supported modules. KLM is running centrally in the Kyma Control Plane and is configured with Kyma custom resource in the namespace kyma-system located in the managed cluster. Users who want to use some managed modules have to add their names to the Kyma CR spec. The community modules cannot be managed by the KLM and should be installed with the desired version using kubectl with the provided Kubernetes manifests (manager deployment and default configuration).
The situation gets more complicated when users want to install the "manageable" modules in their own (not managed) cluster (like k3s) or if they want to opt-out from full management in the managed cluster (install module manager with kubectl without using KLM).

Having a list of available modules with clear indicators if the module is/can be fully managed or not, and a consistent convenient installation process is a must-have.

Acceptance Criteria

• Installing Community Module - Install community modules (not managed) #3350
  • take data from .spec.resources from ModuleTemplate and deploy it on the cluster
  • add a separation for Community Modules in the Add Modules view
  • all of the previous functionalities must work (channels, versions, icons, documentation, etc)
• Add a separate Table for Community Modules on the Modules list view
  • The table should look similar to the previous one
  • checking the status should be taken from the manager based on the .spec.manager in ModuleTemplate
  • check .spec.customStateCheck functionality from ModuleTemplates
  • all of the previous functionalities must work (channel, version, beta, documentation, etc)
• Add a separate section for Community Modules in the Edit view of the Modules
  • all of the previous functionalities must work (channels, versions, beta, documentation, etc)
• Add deleting functionality for Community Modules
  • remove all of the resources and manager
• Adjust or add documentation for all of the new functionalities
• Adjust or add tests for all of the new functionalities
• Request a review from UXes of new views and proposals

Attachments
Community modules in managed and non-managed environment - issue with flow, diagrams and reasons