Reconnect UI component

[guardrex]

Fixes #34813

Notes

• I'm versioning all of the 10.0 or later content into one moniker range, and I'm disabling all of the existing content for <10.0. In the past, I broke up coverage into multiple moniker ranges because parts of the coverage changed (e.g., filenames, file locations).
• I'm using our standard approach for cross-linking reference source. I link the main branch, and I include the guidance on selecting the correct release branch/tag.

❓Questions❓

• Are the existing images still accurate? If not, I'll make a tracking note to snap and place new shots on Preview 2 release day because I'm not on nightly releases (yet anyway 😄).
  • https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/fundamentals/signalr/_static/reconnection-ui-90-or-later.png
  • https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/fundamentals/signalr/_static/retry-ui-90-or-later.png
• The rejected scenario is a bit confusing: What does the ReconnectModel component display in that scenario? There's no such class (element marked with) "components-reconnect-rejected-visible," and doesn't components-reconnect-failed-visible go to display: none on a rejection? I don't see any styles for components-reconnect-rejected when it's applied to the dialog.
• Are there any gotchas 😈 to call out?

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/fundamentals/signalr.md	aspnetcore/blazor/fundamentals/signalr

[oroztocil]

Sorry for keeping you waiting for the review. I first want to investigate and fix https://github.com/dotnet/AspNetCore-ManualTests/issues/3489 because it might involve changing some things mentioned in the docs.