Using trace on multiple js targets in a compound configuration produces corrupt logs

[nikitalita]

Describe the bug
When using a compound configuration for debugging, vscode-js-debug will write trace logs to the same log file for all targets with trace enabled if they each use vscode-js-debug. This ends up producing corrupt logs.

You'd run into this in attempting to debug electron apps, where you would want to debug the main process and renderer process simultaneously.

To Reproduce
Steps to reproduce the behavior:
I've created a branch in my repo to reproduce this:

1. git clone --branch new-debug https://github.com/nikitalita/steam-gyro-for-cemuhook
2. npm i && npm run build:all-debug
3. Open in VS Code, run debug for "Electron: All" (which should be the default).
4. After the app has finished launching, stop it.
5. Observe in the debug console where it wrote the log for each process (Electron:Main and Electron: Renderer). It should be the same file.
6. Try and upload the resulting log to vscode-pwa-analyzer
7. Analyzer throws an error decompressing.

Log File

Corrupt log file:
vscode-debugadapter-8.json.gz

VS Code Version: 1.50.1

[connor4312]

Thanks for the issue!

Verifiers: this can be reproduced fairly easily using any compound launch config which launches multiple configurations with trace: true