Update dependency @types/chai to v5

[krypton-build-user]

This PR contains the following updates:

Package	Type	Update	Change
@types/chai (source)	devDependencies	major	4.3.20 -> 5.2.3

---

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), 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 Self-Hosted Renovate Bot. Find all logs here.

[krypton-build-user]

⚠ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: chai-as-promised@7.1.1
npm error Found: chai@5.1.2
npm error node_modules/chai
npm error   dev chai@"5.1.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error node_modules/chai-as-promised
npm error   dev chai-as-promised@"7.1.1" from the root project
npm error
npm error Conflicting peer dependency: chai@4.5.0
npm error node_modules/chai
npm error   peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"7.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-10-31T21_03_50_903Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-31T21_03_50_903Z-debug-0.log