refactor: reuse toolbar types and extract mantine context

[YousefED]

• split components and BlockNoteView file for mantine / ariakit / shadcn to cleanup a bit
• extracted generic toolbar types (see packages/react/src/editor/ComponentsContext.tsx). This makes it clear that for example the formattingtoolbar and linktoolbar expect the same types. In the implementations (e.g. mantine/src/components.tsx) we actually pass the same Toolbar (and ToolbarButton) as the different components.

These changes were extracted from the Comments PR, so that it's easy for Nick to continue on this work when working on tables

To discuss

does it still make sense to have a separate FormattingToolbar and LinkToolbar?

Pro:

• makes it easy to pass different components for these different cases (probably pretty niche case)

Con:

• more (internal) code (defining the components)

We could also always use the generic component. And optionally, also pass in a parameter with the "location / usage" (not sure about right naming). e.g., instead of:

<Components.FormattingToolbar.Root>

we do:

<Components.Toolbar.Root usage="formatting-toolbar"

[vercel]

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

Name	Status	Preview	Updated (UTC)
blocknote	✅ Ready (Inspect)	Visit Preview	Feb 17, 2025 1:10pm
blocknote-website	✅ Ready (Inspect)	Visit Preview	Feb 17, 2025 1:10pm

[nperez0111]

This looks good to me