Corrupt logs/trace when debugging a VS Code extension using "type": "extensionHost"

[segevfiner]

Describe the bug
When debugging a VS Code extension using a "type": "extensionHost" debug configuration with "trace": true, the resulting log is corrupted, and you see the log file message printed twice:

Hinting at the same file being written concurrently from two threads/async flows, which leads to its corruption.

To Reproduce
Steps to reproduce the behavior:

1. Generate a new TypeScript VS Code extension using: yo code.
2. Add "trace": true to its launch configuration.
3. Run the extension using the debug configuration.
4. Notice the message about the log file being printed twice, and the resulting log file will be corrupted at the end of the session.

Log File

It's corrupted 😛

VS Code Version: v1.85.2

Additional context