fix(appinsights): explicitly import JS module to fix undefined blazorApplicationInsights

[kolatts]

Summary

• The previous fix (renaming .lib.module.js) was insufficient — the Web UI deployed successfully but the error persisted
• Root cause: Blazor WASM's .lib.module.js auto-loading mechanism is not reliably triggered for NuGet-distributed RCLs, so window.blazorApplicationInsights was never defined at runtime
• Fix: ApplicationInsightsInit.OnAfterRenderAsync now explicitly imports the JS module via IJSRuntime before making any interop calls, guaranteeing the global is defined

The import() call is idempotent — if the module was already loaded by the auto-loading mechanism, the browser returns the cached module with no extra cost.

Test plan

• Deploy to prod, verify no blazorApplicationInsights was undefined error in browser console
• Verify Application Insights receives telemetry with cloud role/instance tags