Add Vaadin react-component into version.json

[mshabarov]

Describe your motivation

Vaadin react-components currently have no split to "core" and "commercial" parts like Vaadin web-components do.

That might lead to a problem of leaking commercial react components into an application that only imports com.vaadin:vaadin-core artifact.

Acceptance Criteria:

• Add react-components into Platform's version.json with no split.
• React-components has a split to "core" and "commercial" components possible in the same way as web-components do, e.g. by having the license entry in the package.json, see Prototype splitting packages [2 days] react-components#229
• Add react-components-core (the name should be discussed, e.g. react-core-components or react-components-all) dependencies into Platform's version-core.json.
• Flow then chooses between react or web-components package/dependency in generated package.json based on the reactRouterEnabled flag in Flow or auto-detection mechanism, see Include react-components into package.json flow#18506.

Additional context

Vaadin/Hilla 24.4.

[manolo]

There is a missing task in the description

• Remove the vaadin-core-versions.json files from hilla and hilla-react artifacts

platform vaadin-core-versions.json brings already hilla-react-components and flow should select the appropriate entries from here depending on the reactRouterEnabled flag or whatever