Update dependency @types/jest to v25.2.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/jest (source)	25.2.1 → 25.2.3

---

Configuration

📅 Schedule: (UTC)

• 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

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

[JiwaniZakir]

The PR title describes this as a simple patch bump of @types/jest from 25.2.1 → 25.2.3, but the package-lock.json changes pull in considerably larger minor version jumps for transitive dependencies — @jest/types, jest-diff, and pretty-format all jump from 25.2.x to 25.5.0. That's worth calling out explicitly in the PR description so reviewers aren't misled about the scope of the update.

The fast-deep-equal change is also structurally significant: the top-level v2.0.1 entry (around line 8822) is removed entirely and replaced with a v3.1.3 entry scoped under ajv's nested dependencies. This is a major version bump for that package (2→3), and since fast-deep-equal v3 drops support for some edge cases with NaN and typed arrays compared to v2, it's worth verifying whether any code paths in this project that rely on ajv's deep-equality behavior could be affected.

The removal of @types/color-name as a required peer of ansi-styles (dropped in 4.3.0) is benign since it was a type-only dependency, but it would be good to confirm no custom color-name type augmentations elsewhere in the project relied on that being present in the dependency tree.