inspector, tracing: Make sure messages are sent on a main thread

[eugeneo]

Fixes: #23185

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[nodejs-github-bot]

@eugeneo build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1812/pipeline

[eugeneo]

@ofrobots
Unfortunately, I do not have access to environment where I could run untrusted code at this moment so I was not able to reproduce the issue and confirm it was fixed.

[ofrobots]

Thanks for the fix @eugeneo. The original test case from #23185 no longer crashes for me with the fix.

[Trott]

CI: https://ci.nodejs.org/job/node-test-pull-request/19170/

[eugeneo]

Looks like there's a race condition that surfaces on Windows.

[eugeneo]

CI is now passing: https://ci.nodejs.org/job/node-test-pull-request/19946/

I will update the commit title and will rebase the change. I also have a follow-up CL that fixes the problem that the bad test case identified.

[Trott]

@nodejs/v8-inspector @nodejs/trace-events

[vmarchaud]

Any news on when this PR could be merged (as well was #24945) ? Currently the inspector based trace_events reporter is broken :(

[eugeneo]

CI: https://ci.nodejs.org/job/node-test-pull-request/20449/

[eugeneo]

The only CI failure is coming from a flaky test that only fails on a single bot.