chore(deps): update shared components packages to v13 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/react	12.1.5 -> 13.4.0
react-i18next	11.18.6 -> 13.5.0

---

Release Notes

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

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.

i18next/react-i18next (react-i18next)

v13.5.0

Compare Source

• self-closing components in translation strings should not attempt to replace the component's children 1695

v13.4.1

Compare Source

• types: use CustomInstanceExtenstions to extend reportNamespaces

v13.4.0

Compare Source

• fix: separate cjs and mjs typings

v13.3.2

Compare Source

• types: fix consider importing '*.js'

v13.3.1

Compare Source

• optimize defaultVariables feature introduced in last release

v13.3.0

Compare Source

• Respect defaultVariables in the interpolation options 1685

v13.2.2

Compare Source

• Fix missing TransWithoutContext type 1672

v13.2.1

Compare Source

• types: Allow iterable ReactI18NextChildren as children 1669

v13.2.0

Compare Source

• Don't use defaults prop as default key 1664

v13.1.2

Compare Source

• postpone usage of newer ES syntax

v13.1.1

Compare Source

• Render all children regardless of type when using i18nIsDynamicList prop 1661

v13.1.0

Compare Source

• Fix non-list dynamic content in Trans component 1660

v13.0.3

Compare Source

• fix unescape is not consistently called for all values 1657

v13.0.2

Compare Source

• export icu.macro 1652

v13.0.1

Compare Source

• types: Fix performance issue in Trans component 1646

v13.0.0

Compare Source

• Update types to support t function redesign 1615
• requires i18next >= v23.0.1

v12.3.1

Compare Source

• optimization for optional lng prop for useTranslation, should now prevent missings when lazy loading translations 1637

v12.3.0

Compare Source

• optional lng prop for useTranslation (helping on server side 1637)

v12.2.2

Compare Source

• try to fix conditional exports in package.json

v12.2.1

Compare Source

• type fix: the type of defaultNS in I18nextProvider should support string[] 1633

v12.2.0

Compare Source

• if defaultValue is passed in not ready t functio (via useTranslation) return that instead of the key, even though the user-land could should be fixed 1618

v12.1.5

Compare Source

• fix react merged types 1606 originally introduced with #​1531 to address #​1506

v12.1.4

Compare Source

• fix crash in gatsby 1594

v12.1.3

Compare Source

• fix fallback of t function in Trans component

v12.1.2

Compare Source

• fix crash in gatsby 1594

v12.1.1

Compare Source

• fix for node resolution 1589

v12.1.0

Compare Source

• context-less version of Trans component to be used for environments without react context 1588

v12.0.0

Compare Source

• Update t function types to rely on types coming from i18next 1501

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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: package-lock.json

npm WARN cli npm v10.2.3 does not support Node.js v18.16.1. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.3 does not support Node.js v18.16.1. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: application-services-ui@0.0.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   dev 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@13.4.0
npm ERR! node_modules/@testing-library/react
npm ERR!   dev @testing-library/react@"13.4.0" 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/8599b0/aa7fd9/cache/others/npm/_logs/2023-11-15T21_35_21_189Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/8599b0/aa7fd9/cache/others/npm/_logs/2023-11-15T21_35_21_189Z-debug-0.log