Remove mutation tracking from the store

[shadaj]

TODO:

• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass
• Update CHANGELOG.md with your change

[stubailo]

I think we could better encapsulate mutationStore, but other than that this looks like a good change!

[stubailo]

Instead of updating these store items directly, can we make the mutation store a class and have methods for each of these situations? Then we can operate on a slightly higher level of abstraction and call something like this.mutationStore.saveMutationError(mutationId, error) (similar to the actions we used to dispatch)

Also, I think this means we don't need the mutation-related Redux actions anymore, right? I guess we should leave them back in for better backwards compatibility?

[stubailo]

Same as above, let's wrap these in some kind of method on mutationStore

[stubailo]

@jbaxleyiii this is a change we want to be really careful with, since it will definitely break something. For example this will break mutations in the dev tools as is since that currently reads from the store.

[stubailo]

Can we open an issue to make sure to clean up old mutations? Right now they all stick around forever (not a regression, just a pre-existing issue).

[jbaxleyiii]

@shadaj @stubailo can you walk me through the goals of moving this and queries out? I'll see if I can find anyone using this in the store aside from the dev tools.