Update dependency next-i18next to v13

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next-i18next	^12.1.0 -> ^13.0.0

---

Release Notes

i18next/next-i18next

v13.2.2

Compare Source

• pageProps may be undefined on strange setups #​2109"

v13.2.1

Compare Source

• types: fix serverSideTranslations args #​2104"

v13.2.0

Compare Source

• types: Update serverSideTranslation args type #​2097"

v13.1.6

Compare Source

• fix: allow user provided affixes to be used without providing localeStructure #​2100"

v13.1.5

Compare Source

• #​2089, more stable impelementation of "feat(server-side): custom default config path #​2084"

v13.1.4

Compare Source

• revert #​2084

v13.1.3

Compare Source

• another code snippet for #​2084 to try to fix for dynamic pages

v13.1.2

Compare Source

• different code snippet for #​2084 to try to fix for dynamic pages

v13.1.1

Compare Source

• log config path if no config found

v13.1.0

Compare Source

• feat(server-side): custom default config path #​2084

v13.0.3

Compare Source

• Error if custom localeStructure provided, but no ns option defined.

v13.0.2

Compare Source

Fix

• Types: DefaultNamespace import, see #​2061.

v13.0.1

Compare Source

Fix

• Fix missing i18n.localeDetection in UserConfig, see #​2057.
• Update examples to latest i18next in #​2058

Caution

If you're experiencing typecheck errors regarding keys: ensure i18next is at least ^22.4.3 in your
package.json (then run install), see #​2058.

v13.0.0

Compare Source

The v13.0.0 release is a major version to improve stability and general experience.
It comes with 2 easy changes related to installation. Existing code shouldn't be impacted.
Details can be found in the UPGRADING.md document.

Breaking changes

• react-i18next and i18next
  have been moved to peer-dependencies. They must be installed
  in your app (#​1966)

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" in timezone America/Los_Angeles, 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: app/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: app@0.1.0
npm ERR! Found: react-i18next@11.18.6
npm ERR! node_modules/react-i18next
npm ERR!   react-i18next@"^11.18.6" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react-i18next@"^12.2.0" from next-i18next@13.2.2
npm ERR! node_modules/next-i18next
npm ERR!   next-i18next@"^13.0.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! 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-03-17T16_03_37_853Z-debug-0.log

[sawyerh]

Seems like this is ultimately blocked by stevensacks/storybook-react-i18next#14

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 13.x releases. However, if you upgrade to 13.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.