Improve Blazor reconnection experience after the server is restarted

[tomerqodo]

Benchmark PR from qodo-benchmark#32

---

Note

Improves resiliency and clarity of Blazor Server reconnection/resume.

• Server: ComponentHub.ResumeCircuit no longer sends client errors or aborts when persisted state is unavailable; relies on client reconnection logic; unit tests updated accordingly
• Web JS: DefaultReconnectDisplay and DefaultReconnectionHandler tweak button visibility and flow (hide resume during reconnect; show resume on resume-failed; stop forcing pause update before resume); UserSpecifiedDisplay exposes remote in events and tracks reconnect state
• Templates: Reconnect modal copy updated to include retry on resume-failed; resume button shown for both paused and resume-failed; JS sets resume-failed state instead of reloading on resume exception
• E2E: New tests validate reload on disconnection without server state and successful resume after client pause; test server startup supports disabling reconnection cache and circuit persistence

^{Written by Cursor Bugbot for commit f287efa. Configure here.}

[tomerqodo]

@cursor review

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Animation not hidden when displaying pause state

Medium Severity

The rejoiningAnimation is not hidden in the update() method's pause branch. When show() is called, it sets the animation to visible (display: 'block'). Previously, update() with type: 'pause' would hide the animation, but that line was removed. Now users will see the pulsing animation alongside the static "The session has been paused by the server." message and Resume button, creating a confusing UI state.