fix(deps): update dependency @testing-library/react to v14

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/react	13.0.0-alpha.5 -> 14.1.2

---

Release Notes

testing-library/react-testing-library (@​testing-library/react)

v14.1.2

Compare Source

Bug Fixes

• revert missing hooks warnings (#​1255) (1c67477)

v14.1.1

Compare Source

Bug Fixes

• log globals warning only once (#​1252) (fd52a59), closes #​1249

v14.1.0

Compare Source

Features

• add warnings when globals are missing (#​1244) (d80319f)

v14.0.0

Compare Source

Bug Fixes

• Prevent "missing act" warning for queued microtasks (#​1137) (f78839b)

Features

• Bump @testing-library/dom to 9.0.0 (#​1177) (6653c23)
• Drop support for Node.js 12.x (#​1169) (9b7a1e2)

BREAKING CHANGES

• See https://github.com/testing-library/dom-testing-library/releases/tag/v9.0.0
• Minimum supported Node.js version is now 14.x

v13.4.0

Compare Source

Features

• renderHook: allow passing of all render options to renderHook (#​1118) (27a9584)

v13.3.0

Compare Source

Features

• Use globalThis if available (#​1070) (c80809a)

v13.2.0

Compare Source

Features

• Export RenderHookOptions type (#​1062) (46b28ad)

v13.1.1

Compare Source

Bug Fixes

• TS: export interface RenderHookResult (#​1049) (9171163)

v13.1.0

Compare Source

Features

• Add renderHook (#​991) (9535eff)

v13.0.1

Compare Source

Bug Fixes

• Specify a non-* version for @​types/react-dom (#​1040) (2a889e8)

v13.0.0

Compare Source

Features

• Add support for React 18 (#​1031) (ccd8a0d)

BREAKING CHANGES

• Drop support for React 17 and earlier. We'll use the new createRoot API by default which comes with a set of changes while also enabling support for concurrent features.
  To opt-out of this change you can use render(ui, { legacyRoot: true } ). But be aware that the legacy root API is deprecated in React 18 and its usage will trigger console warnings.

v13.0.0-alpha.7

Compare Source

Bug Fixes

• Add @types/react-dom as a direct dependency (#​1001) (149d9a9)
• Match runtime type of baseElement in TypeScript types (#​1023) (96ed8da)
• render: Don't reject wrapper types based on statics (#​973) (7f53b56)
• TS: make wrapper allow a simple function comp (#​966) (cde904c)

Features

• Support stable React 18 release (#​1030) (01ec707)

v13.0.0-alpha.6

Compare Source

Bug Fixes

• Resolve warning using the wrong react-dom entrypoint (#​1018) (ba24a4b)

BREAKING CHANGES

• Drop support for React < 18.0.0-rc.1

---

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 has been generated by Mend Renovate. View repository job log here.

[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: ui/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: dndmachine@v2.0.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.0.0" from @testing-library/react@14.1.2
npm ERR! node_modules/@testing-library/react
npm ERR!   @testing-library/react@"14.1.2" 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/2023-12-19T04_12_36_748Z-debug-0.log