module: cache deserialized package scopes

[gurgunday]

ESM loading repeatedly deserializes the same package configuration when resolving package imports and determining the format of relative .js imports. Spreading the configuration invokes its lazy getters, reparsing the imports and exports maps on each lookup

Cache the deserialized configuration by package.json path and reuse it when the serialized fields are unchanged. Each lookup still calls the existing loader method, so live VFS changes and errors remain visible. VFS unmounting clears the cache, and callers continue to receive separate result wrappers.

                                                     confidence   improvement   accuracy (*)    (**)   (***)
module/package-scope-config.js n=10000 entries=0     ***            +83.33 %   ±3.12%  ±4.34%  ±6.08%
module/package-scope-config.js n=10000 entries=20    ***           +207.93 %   ±5.72%  ±8.03%  ±11.37%
module/package-scope-config.js n=10000 entries=200   ***          +2494.96 %   ±59.83%  ±85.90%  ±126.23%
module/package-scope-config.js n=10000 entries=1000  ***          +3577.25 %   ±67.32%  ±96.71%  ±142.26%

Measured on an Apple M5 Pro. Inspired by/continues the work of #60425.

[nodejs-github-bot]

Review requested:

• @nodejs/loaders
• @nodejs/performance