Update dependency jest-junit to v15

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jest-junit	^13.0.0 -> ^15.0.0

---

Release Notes

jest-community/jest-junit

v15.0.0

Compare Source

Remove invalid ESC control sequence from XML output https://github.com/jest-community/jest-junit/pull/230 - by @​stevenxu-db

v14.0.1

Compare Source

Prevent unnecessary duplicate test cases by @​azzlack - https://github.com/jest-community/jest-junit/pull/221

v14.0.0

Compare Source

• Fix getOptions support for Windows machines #​215 by @​mastrzyz
• Failures in Test hooks like "AfterAll" now get shown in the Junit Results #​214 by @​mastrzyz

v13.2.0

Compare Source

Support monorepos better via filePathPrefix option by @​marvinroger - https://github.com/jest-community/jest-junit/pull/209

Fix CI builds for windows and drop support for Node 10.x - https://github.com/jest-community/jest-junit/pull/210

v13.1.0

Compare Source

Configurable test suite properties file location by @​JohanBrorson - https://github.com/jest-community/jest-junit/pull/204

---

Configuration

📅 Schedule: 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

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ 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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: objection-visibility@1.1.0
npm ERR! Found: objection@3.0.0
npm ERR! node_modules/objection
npm ERR!   dev objection@"^3.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer objection@">= 2 < 3" from objection-visibility@1.1.0
npm ERR! node_modules/objection-visibility
npm ERR!   dev objection-visibility@"^1.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: objection@2.2.18
npm ERR! node_modules/objection
npm ERR!   peer objection@">= 2 < 3" from objection-visibility@1.1.0
npm ERR!   node_modules/objection-visibility
npm ERR!     dev objection-visibility@"^1.0.0" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-20T18_58_53_600Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-20T18_58_53_600Z-debug-0.log