refreshAll should work with <mutation>.updates()

Describe the problem

.updates() allows you to opt for a single flight mutation instead of needing two round trips, but only if you refresh the queries individually, on screens with many queries, this is a problem
There is a utility that refreshes all active queries, but it doesn't work with .updates()
Additionally, it would be nice if it were also possible to refresh active queries on the server side, also avoiding the need to refresh each query individually
Assuming there is some record of active queries (or whatever refreshAll uses) mutations could receive this record when triggered and then be given the option to refresh these queries on the server, enabling single-flight-mutations by default for such query

Describe the proposed solution

That refreshAll works with .updates() for single flight mutations and some api to do the same inside mutations

Alternatives considered

Keep a mental map of active queries and refresh them individually

Importance

nice to have

Additional Information

No response

Start by reviewing the existing refreshAll behavior and the .updates() flow, then read the linked discussion for the proposed server-side API. Determine how active queries are tracked and define what support for refreshing them from mutations should look like on both client and server.