Merge remote-tracking branch 'react-query/v4' into 2927-offline-queries

Merge remote-tracking branch 'react-query/v4' into 2927-offline-queries # Conflicts: # src/core/queriesObserver.ts # src/reactjs/useQueries.ts

feat(useQuery): offline queries network mode docs

feat(useQuery): offline queries network mode docs (unfinished)

feat(useQuery): offline queries offline mutations test

feat(useQuery): offline queries add devtools test for offline mock

feat(useQuery): offline queries use a higher retryDelay to make test more stable, otherwise, it might start retrying before we "go offline"

feat(useQuery): offline queries mock useMediaQuery to get rid of unnecessary check in devtools - if window is defined, `matchMedia` is also defined

feat(useQuery): offline queries offlineFirst test

feat(useQuery): offline queries add test for abort signal consumed - different results expected for node < 15 where we don't have AbortController, thus can't consume the signal

Merge remote-tracking branch 'react-query/v4' into 2927-offline-queries # Conflicts: # src/core/query.ts

feat(useQuery): offline queries fix merge conflict and invert condition because no-negated-condition

Merge remote-tracking branch 'react-query/v4' into 2927-offline-queries # Conflicts: # src/core/query.ts

feat(useQuery): offline queries let resolved querie continue, but don't put them in fetching state

feat(useQuery): offline queries avoid the impossible state by not calling config.onContinue for already resolved queries, as that would put them right into fetching state again, without actually fetching

feat(useQuery): offline queries inline canContinue, because it's now only called if the query is in paused state anyways

Merge remote-tracking branch 'react-query/v4' into 2927-offline-queries # Conflicts: # src/core/retryer.ts

feat(useQuery): offline queries make networkMode param mandatory for canFetch (and default to online internally) so that we can't screw that up again

feat(useQuery): offline queries stupid mistake

feat(useQuery): offline queries make sure that optimistic results don't show an intermediate fetching state, but go opmistically to paused instead

feat(useQuery): offline queries show inactive as higher priority than paused

feat(useQuery): offline queries keep the do-not-start logic out of the run function, and thus out of promiseOrValue. if the promise has already been resolved in the meantime, e.g. because of a `cancel`, the run method will just do nothing, while the p...

Revert "feat(useQuery): offline queries" This reverts commit a647f64a051ca4c02a872e7871b4b2ce49aeda2c.

feat(useQuery): offline queries guard against illegal state transitions: paused queries can unmount or get cancelled, in which case we shouldn't continue them, even if we dispatch the continue event

feat(useQuery): offline queries i messed up the icon order

feat(useQuery): offline queries different icons, padding, color

feat(useQuery): offline queries attempt at offline toggle button

feat(useQuery): offline queries okay, pausing multiple times was a bad idea, continueFn() will be called eventually anyways

feat(useQuery): offline queries never stop pausing when continueFn is called. Initially, I only had this guard for when it's called from the outside, e.g. for onWindowFocus while still being offline, but we need this always because otherwise query can...

add paused queries to the devtools.tsx

feat(useQuery): offline queries fix tests that were influencing each other by using proper jest mocks for online and visibility state

feat(useQuery): offline queries tests for networkMode: always