Split into multiple packages?

1. With JSX4 bringing breaking changes, the JSX3 bindings have been moved into a separate namespace ReactV3. I was wondering if this ReactV3 namespace shouldn't better be provided by some compatibility package.
2. @rescript/react currently includes bindings for both react and react-dom and also has both as peer and dev dependencies. However, not every React project is also using React DOM. E.g. React Native projects aren't. So IMHO react-dom bindings should go into their own package.
3. #33 mentions the idea to split out ReScriptReactRouter into a separate package.

If we did all that, we'd end up with something like

• @rescript/react
• @rescript/react-dom
• @rescript/react-jsx3-compat
• @rescript/rescript-react-router (or just rescript-react-router?)

@mattdamon108 @cristianoc What do you think? How would such a split affect the PPX?

Comienza revisando el contenido actual del paquete @rescript/react, sus bindings y dependencias de React y react-dom, así como las referencias a PPX mencionadas en el issue. La tarea estaría completada cuando exista una división acordada de los paquetes que cubra la compatibilidad con ReactV3, react-dom y ReScriptReactRouter, incluido cómo afecta a PPX.