chore(deps): update dependency jest-junit to v17

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
jest-junit	16.0.0 → 17.0.0

---

Release Notes

jest-community/jest-junit (jest-junit)

v17.0.0

Compare Source

Upgrade uuid package to latest - #​284

---

Configuration

📅 Schedule: (in timezone Europe/Kiev)

• Branch creation
  • At 06:00 PM through 11:59 PM and 12:00 AM through 09:59 AM (* 18-23,0-9 * * *)
• 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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a2102d323b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Update the pnpm lockfile with the dependency bump

Because this changes package.json without the matching pnpm-lock.yaml update, installs fail under the repository's normal frozen-lockfile path; I verified pnpm install --frozen-lockfile --ignore-scripts reports ERR_PNPM_OUTDATED_LOCKFILE with jest-junit as lockfile: 16.0.0, manifest: 17.0.0. CI environments use frozen lockfile by default, so this dependency update will block CI until the lockfile is regenerated and committed.

Useful? React with 👍 / 👎.