feat(deps): lock file maintenance

[renovate-bot]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 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 was generated by Mend Renovate. View the repository job log.

[trentm]

npm run compile fails with:

 ../../node_modules/@types/react/index.d.ts:36:53 - error TS7016: Could not find a declaration file for module 'scheduler/tracing'. '/home/runner/work/opentelemetry-js-contrib/opentelemetry-js-contrib/node_modules/scheduler/tracing.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/scheduler` if it exists or add a new declaration (.d.ts) file containing `declare module 'scheduler/tracing';`

36 import { Interaction as SchedulerInteraction } from "scheduler/tracing";
                                                       ~~~~~~~~~~~~~~~~~~~

This is the same issue that Martin hit in #2299 recently, explained here:
#2299 (comment)

tl;dr: I'm pretty sure (I haven't checked yet because yah 23k line package-lock.json diff!) the update includes an update to @types/scheduler (a minor update, but it is in 0.x range) that breaks the @types/react that uses it. I'm guessing that @types/react was not updated. The latest @types/react includes a fix to its dependency range on @types/scheduler that should fix the issue.

[trentm]

tl;dr: I'm pretty sure (I haven't checked yet because yah 23k line package-lock.json diff!) the update includes ...

Confirmed, the diff includes:

     "node_modules/@types/scheduler": {
-      "version": "0.16.8",
-      "resolved": "https://registry.npmjs.org/@types/scheduler/-/scheduler-0.16.8.tgz",
-      "integrity": "sha512-WZLiwShhwLRmeV6zH+GkbOFT6Z6VklCItrDioxUnv+u4Ll+8vKeFySoFyK/0ctcRpOmwAicELfmys1sDc/Rw+A==",
+      "version": "0.23.0",
+      "resolved": "https://registry.npmjs.org/@types/scheduler/-/scheduler-0.23.0.tgz",
+      "integrity": "sha512-YIoDCTH3Af6XM5VuwGG/QL/CJqga1Zm3NkU3HZ4ZHK2fRMPYP1VczsTUqtsf43PH/iJNVlPHAo2oWX7BSdB2Hw==",
       "dev": true
     },

but @types/react is still at the version that doesn't have the fix for this:

% git branch --list
* renovate/lock-file-maintenance
  main

% npm ls --package-lock-only @types/scheduler
[email protected] /Users/trentm/tm/opentelemetry-js-contrib11
└─┬ @opentelemetry/[email protected] -> ./plugins/web/opentelemetry-plugin-react-load
  └─┬ @types/[email protected]
    └── @types/[email protected]

@types/[email protected] has a fix. Can we tell renovate to update that dep as well?
Oh, we'd need to update the pinned version at

opentelemetry-js-contrib/plugins/web/opentelemetry-plugin-react-load/package.json

Line 58 in 9dc55da

"@types/react": "17.0.67",

@pichlermarc Would we prefer that is done in a separate PR? Or update (some of) those devDependencies to caret ranges?