chore(deps): update dependency http-proxy-middleware to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
http-proxy-middleware	^2.0.6 -> ^3.0.0

---

Release Notes

chimurai/http-proxy-middleware (http-proxy-middleware)

v3.0.0

Compare Source

This release contains some breaking changes.

Please read the V3 discussion https://togithub.com/chimurai/http-proxy-middleware/discussions/768
or follow the MIGRATION.md guide.

• feat(typescript): type improvements (#​882)
• chore(deps): update micromatch to 4.0.5
• chore(package): bump devDependencies
• feat(legacyCreateProxyMiddleware): show migration tips (#​756)
• feat(legacyCreateProxyMiddleware): adapter with v2 behavior (#​754)
• docs(proxy events): fix new syntax (#​753)
• feat(debug): improve troubleshooting (#​752)
• test(path-rewriter): improve coverage (#​751)
• feat(ejectPlugins): skip registering default plugins (#​750)
• refactor: logging [BREAKING CHANGE] (#​749)
• refactor(handlers): refactor to plugins [BREAKING CHANGE] (#​745)
• feat(plugins): add support for plugins (#​732)
• docs: fix v3 documentation
• fix: server mounting [BREAKING CHANGE] (#​731)
• test(fixRequestBody): fix broken test
• refactor: use node http base types [BREAKING CHANGE] (#​730) (special thanks: @​cdaringe & @​devanshj)
• feat(option): refactor context to pathFilter option [BREAKING CHANGE] (#​722)
• feat: remove shorthand usage [BREAKING CHANGE] (#​716)

---

Configuration

📅 Schedule: Branch creation - "before 4am 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

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

♻ 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: tournament-scheduler/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!   peer react@">= 16.8" from @culturehq/[email protected]
npm ERR!   node_modules/@culturehq/add-to-calendar
npm ERR!     @culturehq/add-to-calendar@"^1.1.2" from the root project
npm ERR!   18 more (@emotion/react, @emotion/styled, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected]
npm ERR! node_modules/react-text-mask
npm ERR!   react-text-mask@"^5.4.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected]
npm ERR!   node_modules/react-text-mask
npm ERR!     react-text-mask@"^5.4.3" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

File name: global-scoreboard/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!   peer react@">=16.3" from @fortawesome/[email protected]
npm ERR!   node_modules/@fortawesome/react-fontawesome
npm ERR!     @fortawesome/react-fontawesome@"^0.2.0" from the root project
npm ERR!   13 more (@react-aria/ssr, @restart/hooks, @restart/ui, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.3.0" from [email protected]
npm ERR! node_modules/react-bootstrap-table-next
npm ERR!   react-bootstrap-table-next@"^4.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.3.0" from [email protected]
npm ERR!   node_modules/react-bootstrap-table-next
npm ERR!     react-bootstrap-table-next@"^4.0.3" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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