Update dependency @types/mocha to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/mocha (source)	^9.0.0 -> ^10.0.10

---

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

[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: @serenity-js/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/mocha
npm ERR!   dev mocha@"^10.4.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mocha@"^9.2.2" from @serenity-js/[email protected]
npm ERR! node_modules/@serenity-js/mocha
npm ERR!   dev @serenity-js/mocha@"^2.33.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/mocha
npm ERR!   peer mocha@"^9.2.2" from @serenity-js/[email protected]
npm ERR!   node_modules/@serenity-js/mocha
npm ERR!     dev @serenity-js/mocha@"^2.33.8" 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-03-26T18_46_51_263Z-debug.log

[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: @serenity-js/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/mocha
npm ERR!   dev mocha@"^10.8.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mocha@"^9.2.2" from @serenity-js/[email protected]
npm ERR! node_modules/@serenity-js/mocha
npm ERR!   dev @serenity-js/mocha@"^2.33.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/mocha
npm ERR!   peer mocha@"^9.2.2" from @serenity-js/[email protected]
npm ERR!   node_modules/@serenity-js/mocha
npm ERR!     dev @serenity-js/mocha@"^2.33.8" 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-11-21T05_43_18_540Z-debug.log