Dashboard: Add the ability to not persist query data to cache.

[StevenDufresne]

Relates to: #103723

Proposed Changes

There are times when we don't want to add queries to the cache.

Here are some examples of when we don't want to store to cache:

• Time-Sensitive Operations
  • Tokens
• User-Specific Temporary States
  • Shopping Cart
  • Auto-saves
• Large Datasets
  • Search results
  • Analytics data

We currently have this functionality in the state query client, and exclude for TWO_STEP_QUERY_KEY. Let's standardize it.

Testing Instructions

Add { meta: { persist: false } } to any query. Inspect the localStorage cache (REACT_QUERY_OFFLINE_CACHE), expect to not see your query.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-146290

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-146290&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-146290&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~6 bytes removed 📉 [gzipped])

name                    parsed_size           gzip_size
entry-dashboard-dotcom        -46 B  (-0.0%)       -6 B  (-0.0%)
entry-dashboard-a4a           -46 B  (-0.0%)       -6 B  (-0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Sections (~28 bytes removed 📉 [gzipped])

name           parsed_size           gzip_size
site-settings        -46 B  (-0.0%)      -12 B  (-0.0%)
hosting              -46 B  (-0.0%)      -16 B  (-0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications

To test WordPress.com changes, run install-plugin.sh $pluginSlug try/create-way-to-opt-out-of-persistence on your sandbox.

[fushar]

Changes make sense to me 👍