Separate user configured tasks from tasks generated by the extension in `tasks.json`

[jkrech]

Type: Feature Request

Problem to solve:
If the user maintains custom tasks in .vscode/tasks.json this file must be tracked in the source control system (e.g. git).
The CMSIS Solution extension generates tasks into this file based on debugger settings for the active target-set. As a result the tasks.json will show as modified most of the times, however only changes to the user maintained tasks are relevant.

Proposal how this could be solved:
Introduce an input file for the tasks.json that will be appended/prepended (?) to the tasks generated by CMSIS-Solution extension.

e.g. name the file tasks.in.json. Here the user maintains the tasks and this is the file that is maintained under revision control.

As part of the command: cmsis-csolution.updateDebugTasks the tasks from the in file will be added to the tasks.

[JonatanAntoni]

In *nix style systems there is the concept of .d directories. E.g., we could have .vscode/tasks.json.d and .vscode/launch.json.d folders and on update we concat the contents into the actual tasks.json and launch.json files.

A common drawback of using files other than the original ones will be the lack of intellisense when open them in the text editor.

[ReinhardKeil]

@jkrech Is this feature implemented? If so, how?

It might be beneficial to scan two .vscode locations:

1. the directory of the *.csolution.yml file for ./vscode/tasks.in.json. If exist this file will be used - step 2 is skipped then.
2. the workspace directory for the ./vscode/tasks.in.json.

This allows to copy multiple csolution projects into a common workspace.