QuickGrid pagination state lost on navigation or circuit reconnect

Goal: Preserve QuickGrid's PaginationState across page navigation and circuit reconnections in a Blazor Server application so users retain their current page, sort, and filter settings.

Constraints: The PaginationState object is mutable and not serialized automatically; developers must manually persist and restore it. Any solution must stay within the default 256 KB SignalR message size to avoid circuit termination, and must not interfere with component disposal or memory cleanup. It is unclear whether storing state in the URL, protected browser storage, or a server‑side cache offers the best trade‑off between transparency, size limits, and usability.

Questions: What methods can serialize PaginationState while keeping the serialized payload under the 256 KB SignalR message limit? What impact does each storage option (URL query string, protected browser storage, server‑side cache) have on URL length, user experience, and circuit memory usage? What safeguards are needed to prevent displaying stale pagination state when the underlying dataset is updated?