feat: React re-architecture

[matthewlipski]

There are a number of issues with the current rendering implementation in React:

• Each menu/toolbar is rendered under a separate root.
• The editor is not immediately initialized upon calling useBlocknote, causing issues.
• Each menu is attached to document.body instead of being a sibling to the editor.
• The way in which factories are designed makes sense for a vanilla implementation, but using them for React is unintuitive.
• Plugins have too much responsibility - they should only provide information for UI elements to render, but instead they also render the UI elements themselves.
• Supplying custom menu/formatting components is done using the uiFactories option, which is kind of clunky.

This PR is a major rethink of how we create, render, and pass elements to the editor in React (also changes the vanilla implementation a bit).

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
blocknote-website	✅ Ready (Inspect)	Visit Preview	Aug 1, 2023 7:47pm

[YousefED]

added number of comments. Will also create a separate PR with some fixes / changes.

About the overall architecture, I have following questions:

• does it make sense that "static" things like "freezeMenu" are part of "state"? (sorry for opening up this discussion again, seems we're going a bit back and forth)
• Plugin views are recreated indeed when other plugins are changed / added. This is by design in prosemirror, probably so that plugins can react to changes to the view that other plugins make. Although it works (see my separate PR that fixes the issues you ran into with this), I think it will be nicer (and faster) to register all plugins on editor instantation

After the comments have been addressed, lets discussed this including your bullets above that haven't been addressed yet