Add possibility to easily manage unmanaged module

[pPrecel]

Description

Now if a module is configured as unmanaged on the Kyma CR level, it's not possible to turn it managed without editing raw yaml. The following screenshot shows an unmanaged serverless module:

The Edit view should have checkbox for every module to easily enable/disable management of every module. Now it looks like this:

[janmedrek]

~Hey @pPrecel, from KLM's perspective the re-managing of modules is not yet supported, this is rather one-way story until we implement this ticket: https://github.com/kyma-project/lifecycle-manager/issues/1667~

Update: re-managing of the modules is supported with a default approach - this means that the whole module deployment will be updated to the current version available in the channel (if multiple module versions were skipped and module introduced some breaking changes it may go bad).

[janmedrek]

We could provide users with such an option, it would be nice to have a clear warning on the risks though: The re-managed module will be updated to the current active version of the module in the channel. If multiple versions were skipped and breaking changes were introduced in the meantime, the migration may not be automatic and manual adjustments will be needed. Proceed at your own risk.

[mrCherry97]

Hi @pPrecel We need to make a few adjustments to the editing modules flow.

Acceptance criteria:

• [ ] add checkbox/switch in Edit view managed/unmanaged
• [ ] label in status should be adjusted to information
• [ ] add warning when the user is trying to save manage to unmanaged change
• [ ] add information when the user is trying to save unmanaged to manage change
• [ ] check why details are not working after setting to unmanaged
• [ ] contact flow with the UXes and decide if we need to use a checkbox or switch