Blazor 6.0 query string enhancements

[guardrex]

Fixes #22689
Addresses #22045

Internal Review Topic (links directly to the NavManager table section; the Query strings section immediately follows)

Mackinnon ...

• I'd normally 🛌😴 one more night, but let's get this in quickly 🏃. It will be reviewed again at RC.

• Most of this PR pertains to the query string bits, but I do add the replace guidance for NavigateTo while I'm here.

• URI vs. URL: The API rightly uses "URI" ... but for practical purposes around the doc set, we use URL because that's specifically and usually what the dev is working with. Here, "URI" is used in text near API remarks, and "URL" is generally used elsewhere.

• + and %20 in encoding. Let's NOT get deep into the weeds on it! 😄 lol ... There's a delta in the blog post remarks/examples. I think we want %20 everywhere.

• WRT the example tables for URL mods: Don't sweat what looks like awfully wide table cells at this point. Yes! ... they are scary 😨 W....I....D....E for rendering 😄. I want to see how they render in the live topic, then I'll make mods to the display on a follow-up PR as needed. I gave your test code names the Rex treatment 😆 ... movie stars from Serenity.

  

  Can't stop the signal, Mack. Everything goes somewhere, and I go everywhere. - Mr. Universe (David Krumholtz)

  Quote ©2005 Universal Pictures: Serenity https://www.uphe.com/movies/serenity David Krumholtz on IMDB: https://www.imdb.com/name/nm0472710/

[MackinnonBuck]

Looks awesome! Just a small suggestion relating to the removal some functionality from GetUriWithQueryParameter. The tables are a great idea - I agree they are a useful way to illustrate the exact behavior of these APIs. I also agree that it's fine to use %20 everywhere.