fix(vite): evaluate transitively bundled deps on first use - #11465

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/DevelopmentWorkflow.md#running-unit-tests-application.
• Tests for the changes are included - https://github.com/NativeScript/NativeScript/blob/master/tools/notes/WritingUnitTests.md.

What is the current behavior?

The dev deps bundle registers every node_modules file it discovers through a static import *, including files it only reached transitively. All of them are therefore evaluated when the bundle loads. Some of those modules are only ever require()d inside a try/catch by the code that uses them, and throw by design on a platform they don't support. Evaluated eagerly, the throw escapes that guard and aborts the whole dev session.

What is the new behavior?

Files that are only reached transitively are registered behind a getter that evaluates them on first read, as the dependency graph would. The first read replaces the getter with the namespace. CommonJS files get the same namespace shape esbuild's import * gives (named exports, the module as default unless it's __esModule). Entry files are still imported eagerly.

Tests: packages/vite/hmr/server/deps-bundle.spec.ts has an end-to-end esbuild case where a package guards a require of a dependency whose file throws on evaluation. Loading the bundle doesn't throw, the guarded require still catches it, and reading the key directly still throws. There are also entry-code cases for ESM and CommonJS lazy files. All 51 tests in the file pass.