lib: explicitly initialize debuglog during bootstrap

[joyeecheung]

lib: move format and formatWithOptions into internal/util/inspect.js

So these can be required without requiring the whole util.js.

process: call prepareMainThreadExecution in all main thread scripts

lib: explicitly initialize debuglog during bootstrap

This patch splits the implementation of util.debuglog into a
separate file and explicitly initialize it during pre-execution
since the initialization depends on environment variables.
Also delays the call to debuglog in modules that are loaded during
bootstrap to make sure we only access the environment variable
during pre-execution.

Checklist

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

[nodejs-github-bot]

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

[joyeecheung]

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

[joyeecheung]

Landed in f617a73...b05fd4b

[MylesBorins]

It looks like this may have broken our downstream modules fork

nodejs/ecmascript-modules#53

More to come as I dig in and figure out exactly what is going on

[joyeecheung]

@MylesBorins My guess is there's something in the fork that loads debug during bootstrapping which is exactly what this PR tries to forbid. You can instantiate debuglog lazily only when debug is called, similar to how its done in this PR in multiple modules loaded during bootstrap. e.g. for streams:

// Don't do this in the top scope if it's loaded during bootstrap
const debug = require('util').debuglog('stream');

// Do this
let debuglog;
function debug(...args) {
  if (!debuglog) {
    debuglog = require('internal/util/debuglog').debuglog('stream');
  }
  debuglog(...args);
}

[MylesBorins]

thanks @joyeecheung. it looks like the file being required uses the above pattern... and I had a bit of an issue tracking down where the call to debug was happening in the wrong order. I opted instead to lazyload the instantiation of the CJSLoader

see nodejs/ecmascript-modules@02bcd09 for attempted fix. Have a feeling this requires more attention, but appears good enough to move things forward for now

[BridgeAR]

This does land land cleanly on v11.x. It relies on #26466. As soon as that is backported, this should also land cleanly.

[refack]

Cross-ref: PR to backport #26466 #26662