Add an analyzer to warn about code that runs after calling NavigationManager.NavigateTo in server side contexts

[javiercn]

We used to throw a navigation exception and that would stop the execution. this was unique on an SSR context and we switched to just signal the navigation and stop the rendering after the current render batch.

As a result, code that was after the NavigateTo instruction wouldn't run, and now it does, and apps need to be aware of that.

Connected report: dotnet/AspNetCore.Docs#37581

[github-actions]

Triage Summary

Area: area-blazor (concerns NavigationManager.NavigateTo behavior in Blazor Server/SSR contexts and a proposed Roslyn analyzer for it)
Type: Feature (requests a new analyzer that does not currently exist)

Potential Duplicates

• None found

Generated by Issue Triage Agent for dotnet/aspnetcore for #69195 · copilot · auto · 52 AIC · ⌖ 20.1 AIC · ⊞ 28.1K · ◷