worker_threads that use es modules incorrectly pause when loaded

<!-- Thank you for reporting an issue. This issue tracker is for bugs and issues found within Node.js core. If you require more general support please file an issue on our help repo. https://github.com/nodejs/help Please fill in as much of the template below as you're able. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or output of `"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"` in PowerShell console (Windows) Subsystem: if known, please specify affected core module name --> * **Version**: 16.0.0 * **Platform**: Win 10 x64 * **Subsystem**: inspector ### What steps will reproduce the bug? It's easiest to run under a debugger that supports worker threads, like VS Code's Node.js debugger. I've created an example repo [here](https://github.com/connor4312/node-38420): 1. Open the folder in VS Code 2. In the debug view (play button on the left hand side), select "No Bug" and hit the play button. This runs `no-bug/index.js`. 3. A worker thread spawns, logs its message, and exits 4. Now select "Bug", and hit the play button. This runs `bug/index.js`: the same code in an ES module. 5. The debugger pauses on the first line in the worker ### How often does it reproduce? Is there a required condition? 100% ### What is the expected behavior? The debugger doesn't pause with ES modules ### What do you see instead? The debugger pauses ### Additional information It looks like Node.js is incorrectly reporting that the program is started with inspectBrk:  VS Code (and Webstorm I think, though I haven't tried to repro there) use a bootloader to inject ourselves into the process via NODE_OPTIONS. We don't actually invoke with --inspect-brk, we [manually call](https://github.com/microsoft/vscode-js-debug/blob/79cee70c3e420555dd0f917550e6a0e659662e6a/src/targets/node/bootloader.ts#L169-L175) `inspector.wait…