[CHORE] Core dependency upgrade

[aristidesstaffieri]

Closes #1824

Re-roll of #1830

Major dependency upgrade for -
react
react-router
typescript
styled-components
clsx
@testing-library/*
@reduxjs-toolkit

Notable changes -
Improved store types
new routing API from react-router v7, significant changes to the routing paradigm and architecture, mostly found in Router.tsx but also impacts all nested routes.

Regressions -
Send/Swap tests are not easily compatible with these changes due to the changes to nested routes. I've commented and detailed the situation and potential ways to revive them in the change set diffs for the tests.

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Deprecated	npm/@types/history@5.0.0	Reason: This is a stub types definition. history provides its own type definitions, so you do not need this installed.	extension/package.json	⚠︎
Deprecated	npm/@types/testing-library__jest-dom@6.0.0	Reason: This is a stub types definition. @testing-library/jest-dom provides its own type definitions, so you do not need this installed.	extension/package.json	⚠︎
Deprecated	npm/@types/qrcode.react@3.0.0	Reason: This is a stub types definition. qrcode.react provides its own type definitions, so you do not need this installed.	extension/package.json	⚠︎

View full report↗︎

Next steps

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@types/history@5.0.0
• @SocketSecurity ignore npm/@types/testing-library__jest-dom@6.0.0
• @SocketSecurity ignore npm/@types/qrcode.react@3.0.0