chore(deps): update dependency jest-watch-typeahead to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
jest-watch-typeahead	^2.2.2 → ^3.0.0

---

Release Notes

jest-community/jest-watch-typeahead (jest-watch-typeahead)

v3.0.1

Compare Source

Bug Fixes

• update ansi-escapes and string-length (#​380) (67d5bff)

v3.0.0

Compare Source

Features

• Update for Jest 30 (#​377) (3009a28)

BREAKING CHANGES

• Drop support for Jest 27, 28 & 29. Drop support for Node 14, 16, 19, 21 & 23

2.2.2 (2023-01-24)

Bug Fixes

• update chalk (#​211) (8c2b064)

2.2.1 (2022-11-16)

Bug Fixes

• deps: update dependency ansi-escapes to v6 (#​183) (8e9713b)
• deps: update dependency slash to v5 (#​186) (726f0d1)

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[sentry]

Bug: Upgrading jest-watch-typeahead creates a version mismatch with the project's core Jest dependency (v29 vs. v30), which may cause runtime errors in Jest's watch mode.
_{Severity: MEDIUM}

Suggested Fix

To resolve the potential runtime conflict, either upgrade the project's core jest dependency to version 30 to match the jest-watch-typeahead peer dependency, or revert the jest-watch-typeahead upgrade to a version compatible with Jest 29. After making changes, verify the fix by running jest --watch.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: frontend-demo/package.json#L72

Potential issue: The update to `jest-watch-typeahead` v3.0.1 introduces peer
dependencies on Jest v30 packages, such as `jest-watcher@^30.0.0`. However, the
project's core Jest version remains `29.7.0`. While the package manager resolves and
installs both versions, this creates a dependency mismatch that could lead to runtime
failures. The issue would manifest specifically when using Jest's watch mode (`jest
--watch`), as the typeahead plugins may attempt to call APIs from Jest v30 that are not
available in the Jest v29 environment, causing the watch plugins to fail.

[sentry]

Bug: The update to jest-watch-typeahead v3 requires jest v30, but the project is still configured to use jest v29, creating an unmet peer dependency.
_{Severity: HIGH}

Suggested Fix

To resolve the peer dependency conflict, update the jest package and its related dependencies (e.g., jest-environment-jsdom) to version 30 in package.json. This will align the Jest version with the requirements of jest-watch-typeahead v3.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: frontend-demo/package.json#L72

Potential issue: This pull request updates `jest-watch-typeahead` to v3.0.1, which has a
peer dependency requirement for `jest` version 30. However, the project's `package.json`
continues to specify `jest` v29.7.0. This version mismatch will cause an unsatisfied
peer dependency. While the dependency installation might only produce a warning, it will
lead to runtime errors when tests are run in watch mode. The `jest-watch-typeahead`
plugin will attempt to call Jest 30-specific APIs that are not present in Jest 29,
causing the test runner to fail. This will break the testing workflow for developers and
in CI/CD pipelines.