Preserve restored query state in persisted snapshots

Normalized profile

What this task asks for

Preserve full persisted query state, including errors, counters, timestamps, and infinite pagination, during restoration and cache rebuilds. A restored query should behave like a real cached query snapshot, not like a fresh successful fetch that only happens to reuse old data. Bulk restoration from fine-grained storage should preserve the same semantics when rebuilding the cache. The solution must add a new public helper exported from query-core named createPersisterRestoreResult. The helper must accept an object with the shape { data, state } and return a value that can be returned from the persister option used by prefetchQuery and query observers to indicate that a persisted snapshot was restored instead of freshly fetched. The restored query must end in fetchStatus set to idle, preserve status including error states, expose isRefetchError when data and error are both present, and retain the provided counters, timestamps, invalidation markers, and infinite-query pagination state. Bulk restoration from fine-grained storage must preserve the same guarantees when rebuilding more than one query from storage.