Fix jest-junit reporter error in CI (#ISSUE)

Resolves the CI failure where jest-junit module could not be resolved
when running tests for react-on-rails-pro-node-renderer package.

Changes:
- Add jest-junit to root package.json devDependencies for workspace-wide availability
- Create babel.config.js for react-on-rails-pro-node-renderer to enable TypeScript transpilation
- Add @babel/preset-env and @babel/preset-typescript to package devDependencies

This ensures the Jest CI reporter can be found and tests can properly
transpile TypeScript files during test execution.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: justin808

package.json

@@ -47,6 +47,7 @@
     "jest": "^29.7.0",
     "jest-environment-jsdom": "^29.7.0",
     "jest-fetch-mock": "^3.0.3",
+    "jest-junit": "^16.0.0",
     "jsdom": "^22.1.0",
     "knip": "^5.46.0",
     "nps": "^5.9.3",

packages/react-on-rails-pro-node-renderer/babel.config.js

@@ -0,0 +1,7 @@
+module.exports = {
+  presets: [
+    ['@babel/preset-env', { targets: { node: 'current' } }],
+    '@babel/preset-typescript',
+    '@babel/preset-react',
+  ],
+};

packages/react-on-rails-pro-node-renderer/package.json

@@ -33,7 +33,9 @@
   "devDependencies": {
     "@babel/core": "^7.26.10",
     "@babel/eslint-parser": "^7.27.0",
+    "@babel/preset-env": "^7.20.2",
     "@babel/preset-react": "^7.26.3",
+    "@babel/preset-typescript": "^7.27.1",
     "@honeybadger-io/js": "^6.10.1",
     "@sentry/node": "^7.120.0",
     "@types/fs-extra": "^11.0.4",