perf(esm-loader): don't parse url if specifier starts with node:

[paul-soporan]

What's the problem this PR addresses?

The ESM loader's resolve hook can skip parsing the URL if the specifier starts with node:.

Addresses #3603 (comment).

How did you fix it?

Extracted isBuiltinModule from applyPatch into nodeUtils and made the ESM loader's resolve hook use it rather than only checking Module.builtinModules.

I also changed the order of the lhs and rhs of isBuiltinModules so that it doesn't have to check the entire set first if the specifier starts with node:.

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[arcanis]

I also changed the order of the lhs and rhs of isBuiltinModules so that it doesn't have to check the entire set first if the specifier starts with node:.

I doubt that makes it faster; in practice very few imports will use the node: protocol, so running the .has first is more likely to return the expected result (without having to process the string first to check for a string we know won't be here). That said, I suspect it has no real bearing either way (since non-node imports are the overwhelming majority of imports and will require both calls anyway), so it's just a nit 🙂