Use setContent for collision resolution

[juliusknorr]

Since tiptap 1.23.2 setContent will dispatch a transaction, so we could preserve the collaboration history with that even when we apply changes from the file from outside:

https://github.com/scrumpy/tiptap/releases/tag/tiptap%401.23.2

[juliusknorr]

@max-nextcloud This would be interesting to reevaluate with the ongoing y.js work if we can resolve the manual file overwrite outside of text more nicely by applying the new document on top of the existing editing session.

[max-nextcloud]

Just talked about this with @juliushaertl. Some points to note:

• if we make locking mandatory (maybe including the locking app in server by default) there would be no need for collision resolution anymore.
• we could improve collision resolution by having one party handle it while the others keep editing using setContetn if the server side version is chosen
• The current version is currently mostly made read only to prevent overwriting the server side file. We could keep the editing alive if we managed to save the conflicting files in different places.

[juliusknorr]

Was done with 7512ef2