overrideTags / overwrite queryCacheKey for mutation

[VaZark]

At the moment mutations are allowed only to invalidateTags generated by queries. However, it is possible to receive the updated value of a resource as a response to a mutation.

We currently have a few endpoints that refetch the data via invalidated tags, despite the fact that the update state is available. This doubles the no of calls required for maintaining the state. We could override the cache manually but that increases the additional logic /boilerplate; Using standard fetch would be far simpler.

An ideal solution would be to allow mutations overwrites the data stored in a queryCacheKey with a overrideCacheKey. Or overrideTags that overwrite the tags associated with Queries

[VaZark]

Of course this comes the caveat that it's completely update to the dev that they do not override incompatible data (or validated via TS)