Export launch configurations from devfile to workspace config file

[RomanNikitenko]

The issue depends on:

• Launch configurations are not available for running  eclipse-theia/theia#8987
• Workspace-scoped launch configurations of multi-root workspace are associated with folders eclipse-theia/theia#8985

The first one is critical for the current issue.

Is your task related to a problem? Please describe.

At the moment launch configurations are exported from the devfile to the config file launch.json in the /workspaceFolder/.theia directory. I don't see any problems for the current behavior, because:

• workspace folder by default is projects
• projects contains all exported from devfile projects
• launch configs placed in /projects/.theia/launch.json file - so - no changes for imported projects
• launch configs are available for running for any imported project

We are going to support Multi-root Che Theia Workspaces by default, please see #17212
We get automatically the following behavior for multi-root workspaces if we don't provide any changes related to mechanism of exporting launch configurations:

• projects is not workspace folder now - each imported project is a workspace folder,
  number imported projects = number workspace folders
• launch configurations are exported from the devfile to each workspace folder, so they are duplicated for each imported project
• after exporting the configurations the workspace has unstaged changes for each workspace folder, so, for example:
  • theia/.theia.launch.json
  • che-theia/.theia.launch.json

Describe the solution you'd like

My propose is exporting launch configurations from devfile to workspace config file, so on workspace level.
Using such approach we could avoid:

• unstaged git changes for each imported project,
• configuration duplication for each imported project
• conflicts with existing configs in /projects/.theia/launch.json file (a project for cloning contains own configs vs configs from devfile)

Please see explanation above ^^.

Describe alternatives you've considered

Additional context

The issue depends on:

• Launch configurations are not available for running  eclipse-theia/theia#8987
• Workspace-scoped launch configurations of multi-root workspace are associated with folders eclipse-theia/theia#8985

The first one is critical for the current issue.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.