Forking or replacing squire

[rezbyte]

I just wanted to note down here that we are effectively maintaining a fork of squire at this point. We have made a number of PRs that directly modify our distribution copy of squire such as #6662, #6394, #6625, #6527.

I think it would be better if we make these changes using squire's original TypeScript codebase in our own fork & then using squire's build system to produce the distribution copy. That way, we do not have to deal with one massive file written in plain JavaScript. It should make updating squire easier too as we can use git to merge our changes with squire's upstream.

The other option I hear often is to replace squire entirely. Perhaps we could investigate tiptap? Although I wonder if it is more effort replacing than forking squire in the future as it depends how well any replacement will be maintained in the future. If the replacement is not maintained in the future, we might end up forking or replacing it again.