feat!: implement write hooks for documents

[achou11]

Closes #20

Introduces the following write hooks:

• useCreateDocument()
• useUpdateDocument()
• useDeleteDocument()

The idea is for the consuming application to wrap these hooks if they want the convenience of hooks scoped to a writeable data type e.g.

function useCreateObservation() {
  const projectId = useCurrentProjectId()
  return useCreateDocument({ docType: 'observation', projectId: projectId })
}

function App() {
  const createObservation = useCreateObservation()
  
  function onPress() {
    createObservation.mutate({ ... }, { onSuccess: (observationDoc) => { ... } })
  }
}

Notes:

• Missing in this implementation is being able to specify an attachmentsToAdd opts. Since this only applies to observations, I was trying - and failing - to have the implementation elegantly handle the polymorphism from a types perspective. For now, will consider that to be an enhancement that can be implemented later if really needed. Will create a more specific issue for this after this has been merged.

• Renames a type that's exported from the package, hence the breaking change notice.

[achou11]

renaming DocumentType to WriteableDocumentType is the breaking change.

[achou11]

wondering if this should be more granular about what it invalidates. right now this invalidates all queries related to the document type for the relevant project, which is potentially invalidating more than necessary. it might make sense to only invalidate the queries as following:

1. Invalidate the 'get many' query without cascading
2. Invalidate the 'get by version id' query with cascading
3. Invalidate the 'get by doc id' query with cascading

I think this would be an optimization, but maybe it's fine to ignore for now. How we currently have it is "safer" despite potentially doing more work than necessary.

[achou11]

similar question about how granular the invalidation should be

[achou11]

similar question about how granular the invalidation should be