chore(deps): update dependency debug to ^4.3.5

This PR contains the following updates:

Package	Type	Update	Change
debug	devDependencies	patch	`^4.3.4` -> `^4.3.5`

Release Notes

debug-js/debug (debug)

### [`v4.3.5`](https://togithub.com/debug-js/debug/releases/tag/4.3.5) [Compare Source](https://togithub.com/debug-js/debug/compare/4.3.4...4.3.5) ### Patch - [`cac39b1`](https://togithub.com/debug-js/debug/commit/cac39b1c5b018b0fe93a53a05f084eee543d17f5) Fix/debug depth ([#926](https://togithub.com/debug-js/debug/issues/926)) Thank you [@calvintwr](https://togithub.com/calvintwr) for the fix.

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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @rollup/plugin-babel@6.0.3
npm error Found: rollup@4.9.6
npm error node_modules/rollup
npm error   dev rollup@"^4.0.0" from the root project
npm error   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0||^4.0.0" from @rollup/plugin-json@6.1.0
npm error   node_modules/@rollup/plugin-json
npm error     dev @rollup/plugin-json@"^6.0.0" from the root project
npm error   2 more (@rollup/plugin-node-resolve, @rollup/pluginutils)
npm error
npm error Could not resolve dependency:
npm error peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-babel@6.0.3
npm error node_modules/@rollup/plugin-babel
npm error   dev @rollup/plugin-babel@"^6.0.3" from the root project
npm error
npm error Conflicting peer dependency: rollup@3.29.4
npm error node_modules/rollup
npm error   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-babel@6.0.3
npm error   node_modules/@rollup/plugin-babel
npm error     dev @rollup/plugin-babel@"^6.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-31T18_48_56_643Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-31T18_48_56_643Z-debug-0.log

Tradeshift / io