Update dependency @types/jasmine to ^3.10.18

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/jasmine (source)	^3.10.4 -> ^3.10.18

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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: tslint-microsoft-contrib@6.2.0
npm ERR! Found: tslint@6.1.2
npm ERR! node_modules/tslint
npm ERR!   dev tslint@"^6.1.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tslint@"^5.1.0" from tslint-microsoft-contrib@6.2.0
npm ERR! node_modules/tslint-microsoft-contrib
npm ERR!   dev tslint-microsoft-contrib@"^6.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: tslint@5.20.1
npm ERR! node_modules/tslint
npm ERR!   peer tslint@"^5.1.0" from tslint-microsoft-contrib@6.2.0
npm ERR!   node_modules/tslint-microsoft-contrib
npm ERR!     dev tslint-microsoft-contrib@"^6.2.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/worker/f1e38c/34a1e0/cache/others/npm/_logs/2023-11-22T01_49_17_457Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/f1e38c/34a1e0/cache/others/npm/_logs/2023-11-22T01_49_17_457Z-debug-0.log