chore: Ensure the same babel config is used across the project in a non conflicting way

[bmartel]

Reason for change

In some cases the development of the frontend code could become conflicting with how we were referencing the babel configs in a few places. For simplicity and compatibility of all scenarios, I have removed the babel config from the web/package.json and moved it to the web/babel.config.json, and made the libraries use the root level config for babel instead of duplicating and using a .babelrc in each module.

[netlify[bot]]

✅ Deploy Preview for label-studio-docs-new-theme canceled.

Name	Link
🔨 Latest commit	b546d9534dc21a7c483d031c914e51436343e953
🔍 Latest deploy log	https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/663cb6a8e803a00008954b43

[netlify[bot]]

✅ Deploy Preview for heartex-docs canceled.

Name	Link
🔨 Latest commit	b546d9534dc21a7c483d031c914e51436343e953
🔍 Latest deploy log	https://app.netlify.com/sites/heartex-docs/deploys/663cb6a89cf95b0008cea0aa

[robot-ci-heartex]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[robot-ci-heartex]

This PR was closed because it has been stalled for 10 days with no activity.