[Blazor] Remove obsolete APIs from Components

[tomerqodo]

Benchmark PR from qodo-benchmark#88

[augmentcode]

🤖 Augment PR Summary

Summary: This PR removes a set of obsolete Blazor/Components public APIs and related back-compat code paths.

Changes:

• Removed obsolete parameters and helpers such as Router.PreferExactMatches and older DataAnnotations validation extension overloads.
• Deleted unused/obsolete types like RemoteBrowserFileStreamOptions, WebEventCallbackFactoryEventArgsExtensions, and SignOutSessionStateManager.
• Simplified WebAssembly auth flows by removing obsolete AccessTokenResult.RedirectUrl/ctor and updating redirect logic to use InteractiveRequestUrl.
• Updated logout handling to rely on the navigation history state-based sign-out request validation only.
• Removed a no-op obsolete init accessor (WebRenderer.RendererId.init).
• Removed legacy WebAssembly JS interop entrypoints (e.g., older InternalCalls.InvokeJS<...>).
• Cleaned up associated unit tests that only exercised the removed obsolete APIs.
• Updated PublicAPI.Unshipped.txt files to record the removals for API-compat tracking.

Technical Notes: The primary behavior changes are confined to WebAssembly authentication/logout and access-token redirect paths; the rest are API surface cleanups with corresponding API-compat annotations.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

AccessTokenResult.InteractiveRequestUrl is nullable, but the null-check for it was removed here; this can now pass a null URL into NavigateToLogin (or hit the ! in the else branch) and throw at runtime. Consider ensuring InteractiveRequestUrl is non-null before navigating (especially since Redirect() can be called regardless of Status).

_{🤖 Was this useful? React with 👍 or 👎}