module: skip preserveSymlinks for main

[guybedford]

The CommonJS module resolver specifically skips --preserveSymlinks for the main entry point into Node.

From discussion in #19383, it seems like this should probably be carried over into the ES module resolver in order to ensure full backwards-compatibility.

The alternative here might be to have --preserveSymlinks act on the main in the CJS resolver too instead of this PR.

//cc @nodejs/modules

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[guybedford]

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

[guybedford]

Not sure if this is due to flaky CI or not... will try again once other CI jobs are looking greener.

[guybedford]

Turns out there was an issue with symlinks on Windows in fixtures, which should be resolved now.

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

[devsnek]

for the commit name, should the subsystem be esmodule or loader or something? module makes me think it touches the cjs module stuff

[guybedford]

CI error this time seems to be completely unrelated, so I believe this is good to merge.

[guybedford]

@devsnek esmodules isn't formally a subsystem I don't believe, although perhaps it should be? That said modules makes sense to me for both too.

[guybedford]

Rebased, latest CI: https://ci.nodejs.org/job/node-test-pull-request/13962/

Will actually merge this time.

[benjamingr]

@guybedford forgot to merge :D ?

[guybedford]

Merged in 141be92.