Fix #123: load NavigationCancelService's JS module lazily, not in the constructor

[devel0peter]

Fixes #123.

NavigationCancelService started a JS interop import in its constructor field initialiser. The service is scoped and resolved during Blazor Server's static prerender pass, where JS interop throws — and since nothing awaits the stored task unless ProceedAsync later runs, the fault surfaced as a TaskScheduler.UnobservedTaskException logged at Error level on every page load of every consuming app, with a finalizer stack that identifies nothing (attributed in MagicSuite via a FirstChanceException stack capture — see MS-25810 / panoramicdata/MagicSuite#102).

The module is now imported on first use inside ProceedAsync: by the time a listener cancels a navigation the circuit is interactive, so the confirm-dialog behaviour is unchanged. PanoramicData.Blazor builds clean with the change.

MagicSuite currently carries a prerender-safe INavigationCancelService override registered after AddPanoramicDataBlazor(); that override will be removed once a version containing this fix is published and consumed.

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
Duplication	0

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}