fix(ssr): avoid resolving ESM for CJS dependencies

[aleclarson]

Description

This PR is related to module resolution in externalized dependencies only.

CJS modules use require, which doesn't support ESM modules, so we can't use the same InternalResolveOptions that are used for import statements within modules transpiled by Vite (aka non-externalized modules).

I've added a tryEsmOnly option to InternalResolveOptions. If this option is true and CJS resolution fails, tryNodeResolve will try ESM resolution options (eg: pkg.module field and import condition in pkg.exports). With this option, CJS resolution is preferred.

Then, we only set tryEsmOnly: true for non-externalized modules, thus ensuring that the hookNodeResolve callback never uses ESM resolution for a CJS importer.

TODO: We might also need to add a preferEsm option to InternalResolveOptions, so Vite projects with type: module in their package.json can avoid Node's CJS compat mode.

Fixes #5673

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[frandiox]

Thanks! Looks like this fixes issues with 2.7.0-beta.0 we had in Hydrogen 🎉