Update dependency http-proxy-middleware to v2.0.10

[konflux-staging]

This PR contains the following updates:

Package	Change	Age	Confidence
http-proxy-middleware	2.0.7 → 2.0.10

---

Release Notes

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

v2.0.10

Compare Source

What's Changed

• fix: harden proxy-table matching to prevent routing bypass by @​G-Rath in #​1268
• ci(github-actions): update publish.yml by @​chimurai in #​1270
• chore(package.json): v2.0.10 by @​chimurai in #​1271

New Contributors

• @​G-Rath made their first contribution in #​1268

Full Changelog: chimurai/http-proxy-middleware@v2.0.9...v2.0.10

v2.0.9

Compare Source

What's Changed

• fix(fixRequestBody): check readableLength by @​chimurai in #​1097
• chore(package): v2.0.9 by @​chimurai in #​1099

Full Changelog: chimurai/http-proxy-middleware@v2.0.8...v2.0.9

v2.0.8

Compare Source

What's Changed

• fix(fixRequestBody): prevent multiple .write() calls by @​chimurai in #​1090
• fix(fixRequestBody): handle invalid request by @​chimurai in #​1091
• chore(package): v2.0.8 by @​chimurai in #​1094

Full Changelog: chimurai/http-proxy-middleware@v2.0.7...v2.0.8

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[konflux-staging]

⚠️ Artifact update problem

Renovate failed to update an artifact 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: yarn.lock

error This project's package.json defines "packageManager": "yarn@4.12.0". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.