chore(deps): update dependency @types/react to v19

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/react (source)	17.0.47 → 19.2.17

---

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

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @cypress/react@5.12.5
npm ERR! Found: @types/react@18.3.1
npm ERR! node_modules/@types/react
npm ERR!   dev @types/react@"18.3.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/react@"^16.9.16 || ^17.0.0" from @cypress/react@5.12.5
npm ERR! node_modules/@cypress/react
npm ERR!   dev @cypress/react@"5.12.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @types/react@17.0.80
npm ERR! node_modules/@types/react
npm ERR!   peerOptional @types/react@"^16.9.16 || ^17.0.0" from @cypress/react@5.12.5
npm ERR!   node_modules/@cypress/react
npm ERR!     dev @cypress/react@"5.12.5" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-27T02_06_02_726Z-debug-0.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: @cypress/react@5.12.5
npm ERR! Found: @types/react@19.2.17
npm ERR! node_modules/@types/react
npm ERR!   dev @types/react@"19.2.17" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/react@"^16.9.16 || ^17.0.0" from @cypress/react@5.12.5
npm ERR! node_modules/@cypress/react
npm ERR!   dev @cypress/react@"5.12.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @types/react@17.0.93
npm ERR! node_modules/@types/react
npm ERR!   peerOptional @types/react@"^16.9.16 || ^17.0.0" from @cypress/react@5.12.5
npm ERR!   node_modules/@cypress/react
npm ERR!     dev @cypress/react@"5.12.5" 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! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-21T20_49_33_904Z-debug-0.log