bootstrap: expose process._rawDebug as a global function

[jsumners]

The process._rawDebug function is very helpful when triaging bugs that cross asynchronous boundaries. It is also quite cumbersome to write out process._rawDebug everywhere such a line is needed. So this change exposes it as a global function to facilitate an improved
developer experience.

If we think that a naming collision is possible, maybe it could be named nodeDebug or similar.

[nodejs-github-bot]

Review requested:

• @nodejs/startup

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.98%. Comparing base (746b17e) to head (12839f9).
Report is 24 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #55907      +/-   ##
==========================================
- Coverage   88.41%   87.98%   -0.44%     
==========================================
  Files         654      653       -1     
  Lines      188036   187868     -168     
  Branches    36187    35890     -297     
==========================================
- Hits       166260   165293     -967     
- Misses      14989    15738     +749     
- Partials     6787     6837      +50     

Files with missing lines	Coverage Δ
lib/internal/bootstrap/node.js	99.58% <100.00%> (+0.01%)	⬆️

... and 103 files with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[jasnell]

Hmmm... I'm not a big fan of adding new Node.js specific globals, and given that process already a global I'm not convinced this really adds much value. I'm willing to be convinced those and won't block this if others find value in it.

[jsumners]

given that process already a global I'm not convinced this really adds much value

In my experience, when someone wants to use this function they are likely going to be writing it in multiple places. I hope we can agree that it is easier, and less annoying, to type out rawDebug than it is to type out process._rawDebug.

Regarding adding Node.js specific globals: isn't that the point of having a specific runtime? To be able to design it such that it provides an environment that is specific to the use cases of the developers that are using it? As an example, at least in Vivaldi and Safari, all Window properties and methods are available without needing to prefix them with window.; i.e. browser runtimes make useful utilities available to users just as being suggested here.