[internal] Upgrade babel runtime

[Janpot]

Was looking through our bundles to debug another issue, and noticed we were compiling in the interopRequireWildcard runtime helper instead of referencing it from @babel/runtime. This upgrades the expected @babel/runtime version to the one we depend on so that babel is up to date about which helpers are available and can use more of them.

[mui-bot]

Netlify deploy preview

https://deploy-preview-43243--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 01d6882

[LukasTy]

Is there a setting to force using the installed version somehow? 🤔
My fear is that we sync it now, but after dependency bumping it will once again get out of sync. 🙈

[Janpot]

Is there a setting to force using the installed version somehow?

I see two ways:

• We could read it from package.json in the build script, and then pass it to babel config in an environment variable.
• Or, we use a pnpm catalog to define a @babel/runtime version in the top-level package.json and read it from there directly in babel config.

I don't think it's a huge problem if it goes out of sync though, the package will be backwards compatible within the same major.

[Janpot]

Looking into this separately. I found a package that is missing @babel/runtime as a dependency. Will add a check for that as well.