fix(template-vite): incorrectly bundling browser entrypoints

[markspolakovs]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• [n/a] The changes are appropriately documented (if applicable).
• [n/a] The changes have sufficient test coverage (if applicable).
• [n/a] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:

In some cases browserField: false in the vite.main.config.js is not sufficient to ensure that the Node version of a package is bundled (or rather, the browser version is not bundled) - in particular where the package uses conditional exports, because Vite's resolver favours conditions over the browser field:

Note this takes lower precedence than conditional exports resolved from the exports field: if an entry point is successfully resolved from exports, the main field will be ignored.

This PR ensures that we set the node condition, which also makes Vite not load the browser version in certain cases.

I've tested this locally using the ws package: before this change it would throw an error when used from the main process (because it has a browser entrypoint that throws), while it doesn't with this change applied to my config.

[caoxiemeihao]

LGTM 👍