fix(vite): shim package roots whose export * targets another bundled package - #11426

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 Vue server strategy pins bare nativescript-vue in the device import map to /ns/m/node_modules/nativescript-vue, expecting that URL to serve the deps-bundle shim. It doesn't: collectDepsModuleExportInfo returns names: null for the package root because nativescript-vue/dist/index.js contains a bare export * from '@vue/runtime-core', and getShimForSpec only emits a shim when the export surface is enumerable. The real file is served per-module instead, so any node_modules file served per-module that imports nativescript-vue bare (for example @nativescript-community/ui-collectionview/vue3) evaluates the root a second time, and its module-scope init() re-registers the core elements:

Error: Element for AbsoluteLayout already registered.

Repro, controls and the NS_VENDOR_INCLUDE workaround are in #11421.

What is the new behavior?

generateDepsBundle now records, from esbuild's discovery metafile, how the bundle actually resolved every bare import edge: importer key → bare specifier → target key (bareImportEdges, persisted in the disk cache; schema bumped so existing caches rebuild). collectDepsModuleExportInfo takes an optional resolver for bare export * targets, and the bundle service backs it with those recorded edges, so the shim enumerates exactly the file esbuild bundled for that importer — no filesystem guessing, no condition lists. If there is no recorded edge, or no resolver, the collector bails to names: null as before and per-module serving is unchanged. With this, nativescript-vue's root gets a real shim and the bare specifier lands in the single bundle realm the strategy already assumes.

Specs: an end-to-end createDepsBundleService case with a fixture root that does export * from 'pkg-i' asserts the served shim re-exports both its own and the target's names through real esbuild; the recorded edges are asserted and round-tripped through the disk cache; collector unit cases cover resolver hit, no edge, and an opaque-CJS target (bails).

Residual risks worth knowing, none new to this change: registry keys collapse nested and hoisted copies of a package to one identity (pre-existing model for every shim); an ambiguous name across two export * targets is unioned and reads as undefined if absent from the bundled namespace, the same behaviour relative stars already have; and the guard that skips namespaced (:) metafile targets has no dedicated spec.

Verified on device with the #11421 repro (blank Vue app importing @nativescript-community/ui-collectionview/vue3, no NS_VENDOR_INCLUDE): the published 8.0.5 crashes with the error above; this build boots cold and from the rebuilt disk cache, the served nativescript-vue URL is the bundle shim, and live edits hot-reload.

Fixes #11421.