fix: use esm entrypoint for css preprocessors and terser

[bluwy]

Description

Alternative to #19182

Use tryNodeResolve instead of require.resolve() for resolving CSS preprocessors and terser. The tryNodeResolve logic and options are extracted from the esbuild config loader resolve.

TODO: Manual testing

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vite@20918

commit: 2dfe88f

[sapphi-red]

I've tested the repo linked in #19182 and it worked 👍

I tested four combinations locally based on https://github.com/hi-ogawa/reproductions/tree/main/vite-19182-sass-tsx

• node + sass-embedded
• node + sass
• tsx + sass-embedded (this was failing before)
• tsx + sass

#19182 (comment)