refactor(angular): consolidate HMR into lib/hmr and strip it from release builds

All HMR support now lives in packages/angular/src/lib/hmr (hmr, route, dialog,
modal-host, cache). Every entry point outside that folder is guarded by
`typeof ngDevMode === 'undefined' || ngDevMode`, so release builds (which define
ngDevMode=false) drop it entirely; verified against iOS and Android release
bundles of a Vite app.

- Features register beforeDispose/afterBootstrap hooks with the reboot instead of
  application.ts importing the router and NativeDialog subscribing to bootstrap
  events; removes the eager-instantiator registry and the ReplaySubject change.
- Route restore captures router.url at dispose and feeds the start path through
  provideLocationStrategy instead of overriding START_PATH, so an app-provided
  START_PATH is no longer clobbered. Route configs are no longer cloned at
  bootstrap; router caches are cleared at dispose instead.
- Dialog restore tracks preserveOnHmr dialogs, drops the destroyed
  viewContainerRef/injector, and waits for app stability so an edited dialog
  inside a lazy route reopens with its fresh class.
- The modal ContentView wrapper and host-prop mirroring apply only in live HMR
  sessions; release and plain dev builds present modals exactly as before.
- Drops the console.warn NG0912 filter, Angular-core namespace holder,
  diagnostics counters, redundant boot-complete globals and the
  import.meta.hot wiring in HmrCacheService (import.meta.hot is always
  undefined inside the package).
- Reverts formatting-only zone-js changes, the NativeDialogModule provider
  removal, the element registration changes and the NSLocationStrategy and
  NSRouteReuseStrategy ngOnDestroy changes.

Author: NathanWalker

packages/angular/src/lib/application.ts

@@ -1,34 +1,10 @@
 import { NgModule } from '@angular/core';
 import { NativeDialogCloseDirective } from './dialog-content-directives';
+import { NativeDialog } from './dialog-services';
 
-/**
- * Convenience module that re-exports the `NativeDialogCloseDirective` for
- * template-driven `[nativeDialogClose]` usage.
- *
- * **Important**: `NativeDialog` itself is **not** listed in this module's
- * `providers` array. The service is `@Injectable({ providedIn: 'root' })`,
- * which already registers a single root-level instance and is fully
- * tree-shakeable. Listing it here as well caused Angular to treat the
- * module-level provider and the `providedIn: 'root'` factory as
- * *separate* registrations once the module was pulled into a standalone
- * app via `importProvidersFrom(NativeDialogModule, ...)`. The duplicate
- * registration triggered:
- *
- *  - Two `NativeDialog` instances in the same root environment injector,
- *    each subscribing to `postAngularBootstrap$`, which produced
- *    duplicate restore attempts during HMR.
- *  - `NG0200: Circular dependency detected for NativeDialog` while a
- *    captured modal was being re-opened during HMR restore, because the
- *    second resolution started while the first was still in progress.
- *
- * Removing the redundant entry collapses both providers back into a
- * single root-level instance, which is what `providedIn: 'root'`
- * documents. App authors who explicitly wire `NativeDialog` themselves
- * (e.g. in a feature module's `providers`) keep working unchanged
- * because they're targeting the same class symbol.
- */
 @NgModule({
   imports: [NativeDialogCloseDirective],
   exports: [NativeDialogCloseDirective],
+  providers: [NativeDialog],
 })
 export class NativeDialogModule {}