trpc 10.7.0 `getQueryKey` => SW & agnostic cache invalidation

[Sheraff]

Every time we need agnostic access to the cache (mainly for cache invalidation on messages from service worker), we should use getQueryKey instead of assuming we know the shape of the key.

• trpc PR: https://github.com/trpc/trpc/pull/3302
• docs: https://trpc.io/docs/useContext#-the-function-i-want-isnt-here

Right now, every version upgrade of tRPC needs to be thoroughly checked because a change in the underlying react-query cache keys and/or request param syntax might not be marked as "breaking" (since most users probably don't rely on them). Having a less leaky abstraction might make the whole thing more robust.

[Sheraff]

getQueryKey doesn't really apply (i think) because we're only "creating keys" from the service worker by intercepting already formed requests