Configuring tasks are broken

[RomanNikitenko]

Bug Description:

There are several problems related to configuring tasks:

1. There are extra fields in the tasks.json file for a configuration after applying Configure Task action for a detected task
   I took the same typescript task for VS Code and for Theia, please compare:

VS Code

Theia

2. There is a duplicate in the list of tasks for running for a detected task after applying Configure Task action, I don't see such behavior for VS Code
   Theia:
   

3. It looks like after configuring a task the configuration from tasks.json file is not taken into account at all - so a user select a configured configuration for running, but the corresponding detected configuration is used instead.

4. Theia allows to edit some fields for a detected task after configuring, but VS Code doesn't. For example, command field for a typescript task.

5. Type is not displayed for tasks items, so it's hard to recognize - if it's a typescript task or npm, for example.
   I created a separate issue for that earlier: Task type is not displayed for detected tasks #9341

Steps to Reproduce:

1. Apply a Configure Task action for a detected task.
2. Try to edit a configuration and run it.
3. You can use Task: Clear History to be sure that you run a configuration from detected or configured section
4. Please see my screenshots and shot videos above.

Additional Information

• Operating System: Fedora
• Theia Version: ab5fef4

[RomanNikitenko]

Using git reset I checked that it's a regression after merging #9189.
So, reviewing the changes provided by #9189 should help to find the cause of the problems...

[vince-fugnitto]

@RomanNikitenko should we think about possibly reverting #9189, it seems to have caused multiple issues related to tasks, for example I am unable to run any task anymore from my example plugin:

• https://github.com/vince-fugnitto/vscode-task-provider-example/releases/download/0.0.3/vscode-task-provider-example-0.0.1.vsix

I verified the commit before works (221d90e).

[RomanNikitenko]

I'm +1 for reverting that changes as there are multiple regressions and I'm not able to help with fixing soon...

[RomanNikitenko]

should be fixed by #9377
@tsmaeder

[tsmaeder]

@RomanNikitenko at least the first issue is fixed. Could you please open separate issues for the many problems in this issue? Having one issue for many problems makes it very hard to track what is fixed and what is not.

[RomanNikitenko]

it's a regression after merging #9189.
that's why I created one issue.
I'm not sure that I should create many issues - first we should check - maybe they were fixed.