[graphql-client] Local-first state management plugin

[agritheory]

Design objectives:

• Server remains long-term source of truth
• Sensitive to "submitted"/ immutable state of documents
• Able to "replay" state when updates (WS/ subscription or HTTP response via GraphQL) received from server

---

User stories

All queries should be normal requests and will not use optimistic updates

Mutations

• Client sends request and does an optimistic update, saving the hash of the request to
• Server responds immediately without commit to DB with hash of request as request id and timestamp
  • whatever action is required is enqueued and handled by the server
• Successfully completed mutations are pushed back to the client and are reconciled in the undo queue as resolved

Network Issue

• In case of a network issue where the server is sending its response to the client, it should inspected the undo queue for unresolved actions and request an update (related to [stonecrop] Undo in Pinia #115)

Errors

• In a case where there's an error, a message is pushed into state and the undo is programmatically triggered (related to [stonecrop] Undo in Pinia #115)

This should be implemented as a finite state machine