Workspace configuration with devfile: synchronization and lifecycle

[slemeur]

Goal

Today, a workspace is getting configured from a multitude of different sources:

• devfile
• tasks.json in a .theia folder
• launch.json in a .theia folder
• and of course, in the IDE with the different configuration options that are available.
  Those are not yet kept synchronized which cause some issues. So if a user is adding a task from the IDE, the menu will guide him into adding a task to the tasks.json file - but then the task is not referenced in the devfile.
  Similarly, if the devfile is getting updated, the workspace will need to be restarted to get the changes applied.

This epic, is a placeholder for analyzing and describing the different requirements around the management of the workspace configuration with the devfile, its synchronization with the IDE and its lifecycle.

Related issues

• Dashboard: While editing a devfile of a workspace, user is constantly interrupted by the auto save
• /projects/.devfile.yaml synchronized with the current workspace devfile
• When creating new tasks for a project imported in a che workspaces, folder with tasks definition should be named '.che'
• che task: Cannot run a che command after workspace restart for some containers
• Task: Changing a command in the devfile of an existing workspace is not taken in account
• Workspace panel is not getting update with newly added task

[slemeur]

Updated the description of #12709 and closing this epic in favor of following in #12709