refactor: prefix built-in node module imports

[slagiewka]

Since v5 relies on node >= 18, this is now possible (since v16, v14.18.0 ¹²).

It's functionally irrelevant:

1. It's not required for CJS nor ESM (with a few exceptions ³)
2. It has no performance promises

However, there are upsides to this approach:

1. It brings clear boundaries to what's a built-in and what's an external dependency
2. It reduces the risk of importing unwanted deps where a built-in is expected
3. It's slightly more interoperable with other JS runtimes that provide node compatibility⁴, albeit only during development. Once imported from npm, built-ins are assumed.

Footnotes

1. https://nodejs.org/docs/latest-v22.x/api/modules.html#built-in-modules ↩

2. https://github.com/nodejs/node/pull/37246 ↩

3. https://nodejs.org/api/modules.html#built-in-modules-with-mandatory-node-prefix ↩

4. https://docs.deno.com/runtime/fundamentals/node/#using-node's-built-in-modules ↩

[UlisesGascon]

Great work @slagiewka! I like the idea, let's see what other @expressjs/express-tc members things about it :)

[carpasse]

LGTM

[IamLizu]

While I appreciate the effort, this isn't necessary. It's only required for newly added built-in modules that conflict with existing ones.

Node.js already prioritizes built-in modules (like http, path, and fs) over user-land modules or files with the same name.

[wesleytodd]

While @IamLizu is technically correct, IMO this is a good change. Being clear is usually better and I personally consider this way border-line best practice at this point. 👍 from me.