Published version on npm pulls in React 19

We have a React 18 project and adding `@grapesjs/react` pulls in React 19 even though `package.json` correctly has `"react": "^18.0.0 || ^19.0.0"` as a peer dependency.

https://github.com/GrapesJS/react/blob/main/packages/grapesjs-react/package.json#L34

The published package on npm has react@^19.0.0 listed as a regular dependency though
```
$ npm view @grapesjs/react dependencies --json
{
"react": "^19.0.0",
"react-dom": "^19.0.0",
"@types/react": "^19.0.0",
"@types/react-dom": "^19.0.0"
}
````

Start with packages/grapesjs-react/package.json at the linked peer-dependency entry, then compare it with the published metadata using `npm view @grapesjs/react dependencies --json`. Done means the published package no longer installs React 19 as regular dependencies and matches the intended React 18/19 peer-dependency range.

Written by the indexing model from the issue text.