docs: reconcile documentation with changes since 10.0.0

[adrianhall]

Summary

Closes #500 — the documentation review/scoping issue tracking drift between docs/, README.md, and everything that changed since the 10.0.0 release.

This PR performs the review described in #500 and fixes every gap found directly, rather than filing separate follow-up issues:

1. README.md prerequisites were stale — said "ASP.NET 8 or later" / ".NET 8 or later" instead of the current 10.x minimum (matches docs/index.md and src/Directory.Build.props's net10.0 target). Also added Blazor WASM to the tested client platform list, which docs/index.md already listed but README omitted.
2. docs/tutorial/client/part-1.md contradicted docs/index.md on the minimum .NET version (".NET 8+" vs ".NET 10.x or later").
3. UnsafeEntityLogging (SECURITY: Add TableOptions flag for unsafe entity logging #446/feat: add UnsafeEntityLogging option to guard entity serialization in logs (#446) #470) was undocumented in the tutorials/samples — prior doc PRs (Examples: Demonstrate UnsafeEntityLogging in the todoapp-tutorial server walkthrough (#446) #476-Examples: Review todoapp-mvc server for UnsafeEntityLogging secure default (#446) #480, docs: demonstrate UnsafeEntityLogging in todoapp-tutorial server walkthrough (#476) #487-fix: resolve remaining sample package drift and Microsoft.OpenApi NU1903 #493) only added UnsafeEntityLogging = false to sample source code comments, never to the actual walkthrough prose in docs/tutorial/server/part-1.md or docs/samples/todoapp/server.md. Both now explain the option, consistent with docs/in-depth/server/index.md. (Also fixed an unrelated pre-existing duplicate base() call in the part-1.md code sample I was already editing.)
4. Stale OpenApi doc page naming — docs/in-depth/server/openapi/net9.md was titled "# .NET 10.x OpenApi support" in its own content, but the filename and mkdocs nav label still said "net9"/".NET 9.x". Renamed to net10.md and updated the nav label and the internal link in docs/in-depth/server/index.md.
5. Blazor WASM sample was undocumented on the site, and a pre-existing docs/in-depth/client/advanced/blazor-wasm.md page (added in (#330) Blazor WASM sample and docs updates. #394, mid-2025) was never wired into the mkdocs nav, making it unreachable via normal site navigation. Added a new docs/samples/todoapp/blazor-wasm.md walkthrough (framed as an online-only client, consistent with the existing "Blazor usage" admonition in the client tutorial) and added both pages to mkdocs.shared.yml's nav. Cross-linked from the tutorial's Blazor admonition.

Out of scope (reviewed, no action needed)

• Internal-only dependency bumps (Update critical severity vulnerabilities in packages #460/fix: resolve transitive package vulnerabilities and update dependencies (#460) #466, Upgrade packages with breaking (major) version changes #465, the Microsoft.OpenApi 2.7.5 pin in Audit sample projects for stale/inconsistent NuGet package pins and NU1903 vulnerability warnings #489/fix: resolve remaining sample package drift and Microsoft.OpenApi NU1903 #493) aren't part of the public package surface consumers reference directly (unlike the SQLitePCLRaw NU1903 note already documented from fix: resolve NU1903 for SQLitePCLRaw.lib.e_sqlite3 by pinning SQLitePCLRaw 3.x #498), so no doc callout was added.
• The create-conflict access-control hardening in SECURITY: Remove conflicting record when IAccessControlProvider says you can't see it #445/fix: hide conflicting record on create when not in IAccessControlProvider view (#445) #471 is a subtle, implementation-detail-level security fix; not surfaced in docs.
• No new/removed sample platforms were found between 10.0.0 and main.

Verification

• mkdocs build and mkdocs build --strict run locally against the changed nav/pages — no broken links, no orphaned-page warnings (the pre-existing mermaid-plugin network-check warning in strict mode is unrelated/pre-existing and not from a docs link).
• Manual diff review to confirm only the intended files changed.