Review use of automerge to check everything looks good

[ben-ryder]

My usage of automerge is mostly based on reviewing the v1 docs and having a bit of a play around. The toolkit package is currently using automerge v2 beta which has API and functionality differences.

I've not noticed anything wrong yet, but I should take the time to understand automerge in more detail (both at a fundamental level and an API interface level) to check I'm not doing anything obviously wrong.

Things to look our for:

• It looks like Table no longer exists, my assumption is that I'll now have to implement this myself in some way.
• It's probably worth thinking about ways to integrate automerge with react/redux state.
• I'm having some issues with TS where an automerge document always has readonly fields so TS complains in change functions. I've solved this by overwriting the typing of the change function, but I should look at this a bit closer and maybe raise an issue as it feels like the library types shouldn't do this by default.

[ben-ryder]

closing for now as I'm pretty sure everything is ok