Adds the Hot Module Replacement runtime layer plus the supporting ESM
resolver hardening and dev-session globals that make hot reload viable on
Android.

* `import.meta.hot`: `data`, `accept`, `dispose`, `prune`, `decline`,
  `invalidate`, `on`/`off`/`send` event surface.
* Dev-session globals (`__nsStartDevSession`, `__nsReloadDevApp`,
  `__nsInvalidateModules`, `__nsRunHmrDispose`, `__nsRunHmrPrune`,
  `__nsHasDeclinedModule`, `__nsKickstartHmrPrefetch`,
  `__nsGetLoadedModuleUrls`, `__nsApplyStyleUpdate`,
  `__nsConfigureDevRuntime`/`__nsConfigureRuntime`,
  `__nsTerminateAllWorkers`).
* Speculative HTTP module prefetch (opt-in) with canonical-key
  normalization so `__ns_hmr__/v<N>` and `__ns_boot__/b<N>` tag prefixes
  share `hot.data` identity across reload cycles.
* ESM resolver hardening in `ModuleInternalCallbacks.cpp` to:
  - Preserve synthetic-namespace identity (`ns-vendor://`, `optional:`,
    `node:`, `blob:`) — these are NOT filesystem paths.
  - Handle HTTP/HTTPS module URLs end-to-end (resolution, fetch,
    canonical-key collapse, dynamic import).
  - Compile `.json` imports into synthetic ES modules.
* Android runtime-dex support for `.extend()` classes created during HMR
  that the static binding generator can't see at build time: runtime DEX
  generation with `$`/`_` inner-class normalization (`DexFactory`),
  dev/HMR class-resolution fallback (`ClassResolver`), and dev-flag /
  `logScriptLoading` plumbing (`AppConfig`, `DevFlags`).

…process

Helpful for programmatic reset of JS isolate for clean restart of JS application as well as OTA (over-the-air) updates without restarting the entire app process.

…ory (#1976)

A dynamic import() with a relative specifier from a module loaded over file:// resolved against the application root instead of the importing module's own directory, so a module outside the app root could not resolve its relative dependencies. ImportModuleDynamicallyCallback only used the referrer URL for http(s) referrers; for file:// it passed an empty referrer and the resolver fell back to the app root. Anchor the specifier at the referrer's directory from resource_name and pass the resolver an absolute file:// URL. Static imports are unaffected. Adds test-app specs for ./ and ../ dynamic imports from subdirectories plus an app-root control.

#1977)

ResolveModuleCallback builds the on-disk path for a relative specifier without collapsing "." and ".." segments, so the same file imported as "./x" from /a/b and as "../x" from /a/b/c lands under two different registry keys. stat() resolves the segments so both locate the file, but the differing keys make V8 compile and evaluate the module twice: two instances with separate state, and import.meta.dirname becomes "/a/b/c/.." for the ".." spelling. Normalize the resolved path before it becomes the registry key, the same way the HTTP branch canonicalizes through CanonicalizeHttpUrlKey. The pass is lexical and runs for every on-disk candidate kind, and is a no-op for already-canonical paths.

…ract

The runtime explicitly does not implement HMR policy. import.meta.hot, the
hot-data/accept/dispose/prune registries, and dev-session state move to the
JS HMR clients (eg, @nativescript/vite); native keeps only the sync HTTP
module fetch, prewarm cache + list-mode kickstart, eviction plumbing, and
the dev-boot-complete signal. Dev helpers are consolidated under __NS_DEV__.

Also fixes dynamic import() error propagation: with top-level-await enabled,
Module::Evaluate() returns a promise instead of an empty MaybeLocal on throw,
so the previous empty-check never fired and import() resolved a
half-evaluated namespace, silently swallowing module evaluation errors. The
callback now checks Module::GetStatus() for kErrored (HTTP, blob, and
generic paths) and rejects with the module's real exception, matching iOS.
Removes the httpModulePrefetch app-config flag and speculative prefetching;
list-mode kickstart remains.

… guards

The V8 ValueSerializer worker messaging on this branch legitimately does
not throw for circular objects; the suite at 3a262b9 gates the legacy
JSON-serializer expectation to JSC and runs structured-clone round-trip
specs instead.

…from the boot archive

The JS bootstrap downloads the dev server's /__ns_dev__/boot-archive
(NDJSON of {url, body} entries) and seeds them directly into the one-shot
prewarm cache consumed by HttpFetchText during V8's synchronous module
walk — replacing hundreds of serial kickstart fetches with one payload.
Mechanism only: the server computes the closure and bodies; the runtime
stores them behind the same gates as kickstart prefetch. Returns
{ ok, seeded, bytes } so callers can fall back to kickstartPrefetch.

[skip ci]

…-integrated

# Conflicts:
#	package.json
#	test-app/runtime/src/main/cpp/ModuleInternalCallbacks.cpp

…-integrated