fix(deps): update dependency @reduxjs/toolkit to v1.9.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@reduxjs/toolkit (source)	1.9.6 -> 1.9.7

---

Release Notes

reduxjs/redux-toolkit (@​reduxjs/toolkit)

v1.9.7

Compare Source

This bugfix release rewrites the RTKQ hook TS types to significantly improve TS perf.

Changelog

RTKQ TS Perf

A number of users had reported that Intellisense for RTKQ API objects was extremely slow (multiple seconds) - see discussion in #​3214 . We did some perf investigation on user-provided examples, and concluded that the biggest factor to slow RTKQ TS perf was the calculation of hook names like useGetPokemonQuery, which was generating a large TS union of types.

We've rewritten that hook names type calculation to use mapped types and a couple of intersections. In a specific user-provided stress test repo, it dropped TS calculation time by 60% (2600ms to 1000ms).

There's more potential work we can do to improve things, but this seems like a major perf improvement worth shipping now.

What's Changed

• chore: Switch 4.9.2-rc to 4.9.5 since 4.9.5 has been released in TypeScript by @​kahirokunn in https://github.com/reduxjs/redux-toolkit/pull/3772
• Copy of "Work around known TS bug with type inference #​3761" by @​julian-ford in https://github.com/reduxjs/redux-toolkit/pull/3777
• Rework named hooks type (v1.9) by @​EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/3769

Full Changelog: reduxjs/redux-toolkit@v1.9.6...v1.9.7

---

Configuration

📅 Schedule: 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   typescript@"5.2.2" from the root project
npm ERR!   typescript@"^4.6.4 || ^5.0.0" from @commitlint/[email protected]
npm ERR!   node_modules/@commitlint/load
npm ERR!     @commitlint/load@"^17.7.2" from @commitlint/[email protected]
npm ERR!     node_modules/@commitlint/cli
npm ERR!       dev @commitlint/cli@"17.7.2" from the root project
npm ERR!       1 more (commitlint)
npm ERR!   5 more (cosmiconfig, cosmiconfig-typescript-loader, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from [email protected]
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from [email protected]
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/1661fc/5bd899/cache/others/npm/_logs/2023-10-20T01_03_09_090Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/1661fc/5bd899/cache/others/npm/_logs/2023-10-20T01_03_09_090Z-debug-0.log