Debug configuration fix

[Christellah]

Description:

Solving some issues with the Debug Configuration :

• Works with vsix (see this bug)
• Doesn't override Python's debugging : issue Pacifica breaks debugging in Python #67
• Prevent opening an output tab on extension's activation : Pacifica output tab is opened whenever Python debugging starts #81
• You can use the drop down to choose Pacifica Simulator Debugger configuration and run it even without having a launch.json

Most of those issues were fixed by adding configuration.type = 'pacifica' instead of python, this way VS Code is not confused by which extension has to resolve the debugging session : ours starts and change the parameters to use our script then change the configuration.type = 'python' so the Python extension can take over and do the real debugging.

Make sure you delete your previous launch.json files and regenerate them as they will no longer work.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Limitations:

You'll need to open a folder in order to use it, but this might be link to the entire extension limitation.

Testing:

• Try running a debug session, Pacifica's and Python and make sure the simulator/output tab is opening at the right moment
• Make sure the debugging is working in vsix (you can fill the package.json fields then run the command npm run package then install the vsix from it)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[LukeSlev]

Sweet fix 🔥👏🙌✔👍👌