Resolves #35

This adds a way to adopting persisted-operations within fuse, this leverages an exchange to take the pre-computed documentId from the document and sends it for mutations/queries. When we see queries the exchange will cast this to a GET operations to improve browser cache-ability of operations.

This is focussed currently on the Next.js way where we have our datalayer co-located with our front-end. This does not facilitate mobile/... clients yet, to do so we might need to expand the options of our route-handler to fetch persisted hashes from a Key-value store. We could facilitate pushing to i.e. Redis/... in a CLI and then configure our GraphQL endpoint to pull from there when a hash comes in.

Something that I would still like to improve here is the fact that you need to manually pass in the .json file. I was thinking that this could maybe be a fairly automatic adoption journey where you are opted into this automatically and need to opt-out explicitly.

Would be eager to hear peoples thoughts here

Personally I gravitate towards supporting a K/V store like Redis, ... or the JSON file for the simple case where we only have i.e. a co-located Next.JS application 😅 added an example how it could look like with vercel/kv

One downside here is that our codegen relies on the server running which could be a cascading effect when you import the persisted operations json but it doesn't exist yet 😅