When creating new tasks for a project imported in a che workspaces, folder with tasks definition should be named '.che'

[slemeur]

Description

When the user is creating (or editing pre-defined) tasks and launch configurations, there is a new folder that is getting created in the source code of the project named .theia.
That should not be the case when you are in the context of Che. The definition of the tasks are going to be che specific, so the folder should be named .che.

If in the project, the folder .theia or .vscode already exist, then we should use that and not "recreate" a new .che folder.

[davidwindell]

@slemeur would implementing this mean that we could commit our theia commands to our project repos in a .theia or .vscode folder? That would be awesome if those were then detected by the IDE as described in #12709

This would be particularly useful as commands can often update throughout the lifecycle of a project and it isn't practical to ask users to update their ws/devfiles all the time.

[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.