Overhaul graphql client cache invalidation

[DingDongSoLong4]

This is a complete rework of the client-side cache invalidation done after mutations are run. I've tried my best to have it refetch as little as possible while avoiding displaying stale data, but it's possible I could have missed some edge cases.

The main issue this should solve is the first part of #3891, where previously creating a new performer/studio/tag would cause massive slowdowns and excessive database queries. What was happening is that the Create mutations were invalidating the All(Performers/Studios/Tags)ForFilter queries, which are slow and expensive queries, especially with very large databases. Invalidating those queries is not necessary, we can make the change client-side by just appending the new object to the end of the list.

There should also be fewer unnecessary queries after mutations, and less stale data in the UI:

• no "FindStudio" for the new studio after a "StudioCreate", for example
• no "FindStudio" for studio id 10 after a "StudioDestroy" for studio id 10
• The stats page is automatically updated client-side for things like creating/destroying studios, tags, etc, so no refetch is required
• A scene's play count, play duration, etc are now updated client-side after running the activity tracking mutations, meaning the activity data in the "File Info" tab now gets updated live as the scene is watched.

And then I've also added the graphql directory to the prettier command to format the schema files, since prettier supports graphql and some of those files are quite badly formatted right now.

Fixes #3815 (I believe)