chore(deps): update dependency eslint-plugin-jest to v29

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-jest	28.14.0 -> 29.1.0

---

Release Notes

jest-community/eslint-plugin-jest (eslint-plugin-jest)

v29.1.0

Compare Source

Features

• prefer-lowercase-title: allow ignoring todos (#​1843) (4658638)

29.0.1 (2025-06-18)

Bug Fixes

• update semantic-release config so new v29 major is marked as latest on npm (#​1772) (531c8ba)

v29.0.1

Compare Source

Bug Fixes

• update semantic-release config so new v29 major is marked as latest on npm (#​1772) (531c8ba)

v29.0.0

Compare Source

Bug Fixes

• remove jest/no-alias-methods from styles config (d3bf1dc)

Features

• drop support for [@typescript-eslint](https://redirect.github.com/typescript-eslint) v6 (fe61a40)
• drop support for [@typescript-eslint](https://redirect.github.com/typescript-eslint) v7 (5ca65d3)
• drop support for ESLint v7 (b06e7d0)
• drop support for ESLint v8.x prior to v8.57.0 (d79765a)
• drop support for Node v16 (aaf62cd)
• drop support for Node v18 (598880c)
• drop support for Node v20.x prior to v20.12.0 (2f2fb68)
• drop support for Node v21 (a366393)
• drop support for Node v23 (1fb1a67)
• unbound-method: remove docs.recommended and docs.requiresTypeChecking properties (945651c)

BREAKING CHANGES

• dropped support for ESLint v8.x prior to v8.57.0
• dropped support for Node v20.x prior to v20.12.0
• dropped support for Node v23
• dropped support for Node v18
• unbound-method: removed docs.recommend and docs.requiresTypeChecking from unbound-method
• dropped support for @typescript-eslint v7
• dropped support for @typescript-eslint v6
• jest/no-alias-methods has been removed from the styles config as its already in
  the recommended config
• dropped support for ESLint v7
• dropped support for Node v21
• dropped support for Node v16

---

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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-plugin-jest@29.1.0
npm error Found: @typescript-eslint/eslint-plugin@6.21.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm error   peer @typescript-eslint/eslint-plugin@"^5.13.0 || ^6.0.0" from eslint-config-airbnb-typescript@17.1.0
npm error   node_modules/eslint-config-airbnb-typescript
npm error     dev eslint-config-airbnb-typescript@"17.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @typescript-eslint/eslint-plugin@"^8.0.0" from eslint-plugin-jest@29.1.0
npm error node_modules/eslint-plugin-jest
npm error   dev eslint-plugin-jest@"29.1.0" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/eslint-plugin@8.47.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   peerOptional @typescript-eslint/eslint-plugin@"^8.0.0" from eslint-plugin-jest@29.1.0
npm error   node_modules/eslint-plugin-jest
npm error     dev eslint-plugin-jest@"29.1.0" 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 /runner/cache/others/npm/_logs/2025-11-18T12_49_12_083Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-18T12_49_12_083Z-debug-0.log