chore(deps): update dependency @rollup/plugin-babel to ^6.0.4

This PR contains the following updates:

Package	Type	Update	Change
@rollup/plugin-babel (source)	devDependencies	patch	`^6.0.3` -> `^6.0.4`

Release Notes

rollup/plugins (@rollup/plugin-babel)

### [`v6.0.4`](https://togithub.com/rollup/plugins/blob/HEAD/packages/babel/CHANGELOG.md#v604) [Compare Source](https://togithub.com/rollup/plugins/compare/7f90b607eda51bbc63e3409f470c1e51af148b70...a1a63fb6b88431f953e1a22af9f2d902e239689e) *2023-10-05* ##### Bugfixes - fix: ensure rollup 4 compatibility [#1595](https://togithub.com/rollup/plugins/pull/1595)

Configuration

:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - "every weekday in 2125" in timezone Europe/Copenhagen.

:vertical_traffic_light: Automerge: Enabled.

:recycle: Rebasing: Never, or you tick the rebase/retry checkbox.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:warning: Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

:recycle: Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN config cert `key` and `cert` are no longer used for most registry operations.
npm WARN config Use registry scoped `keyfile` and `certfile` instead.
npm WARN config     Example:
npm WARN config     //other-registry.tld/:keyfile=/path/to/key.pem
npm WARN config     //other-registry.tld/:certfile=/path/to/cert.crt
npm WARN config key `key` and `cert` are no longer used for most registry operations.
npm WARN config Use registry scoped `keyfile` and `certfile` instead.
npm WARN config     Example:
npm WARN config     //other-registry.tld/:keyfile=/path/to/key.pem
npm WARN config     //other-registry.tld/:certfile=/path/to/cert.crt
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @rollup/plugin-commonjs@25.0.0
npm ERR! Found: rollup@4.9.6
npm ERR! node_modules/rollup
npm ERR!   dev rollup@"^4.0.0" from the root project
npm ERR!   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0||^4.0.0" from @rollup/plugin-json@6.1.0
npm ERR!   node_modules/@rollup/plugin-json
npm ERR!     dev @rollup/plugin-json@"^6.0.0" from the root project
npm ERR!   3 more (@rollup/plugin-node-resolve, @rollup/pluginutils, @rollup/plugin-babel)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional rollup@"^2.68.0||^3.0.0" from @rollup/plugin-commonjs@25.0.0
npm ERR! node_modules/@rollup/plugin-commonjs
npm ERR!   dev @rollup/plugin-commonjs@"^25.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: rollup@3.29.4
npm ERR! node_modules/rollup
npm ERR!   peerOptional rollup@"^2.68.0||^3.0.0" from @rollup/plugin-commonjs@25.0.0
npm ERR!   node_modules/@rollup/plugin-commonjs
npm ERR!     dev @rollup/plugin-commonjs@"^25.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-05T11_05_03_601Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-05T11_05_03_601Z-debug-0.log

Tradeshift / io