fix(deps): update dependency i18next to v23

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
i18next (source)	^22.4.15 -> ^23.0.0

---

Release Notes

i18next/i18next (i18next)

v23.2.11

Compare Source

• types: Fix $TFunctionBrand 1997

v23.2.10

Compare Source

• types: emit function can have additional arguments 1993

v23.2.9

Compare Source

• types: Add brand to TFunction type so different namespaces' TFunctions are not treated as compatible 1994

v23.2.8

Compare Source

• types for hasLoadedNamespace

v23.2.7

Compare Source

• fix utils import (for Deno)

v23.2.6

Compare Source

• Re-allow unknown keys, when a defaultValue is provided 1867

v23.2.5

Compare Source

• Clean language code before passing to formatters 1988

v23.2.3

Compare Source

• types: Optimize logic for fallback ns 1984

v23.2.2

Compare Source

• types: try to fix fallbackNS type handling also for older TS version 1981

v23.2.1

Compare Source

• types: Fix $TFunctionBrand 1997

v23.2.0

Compare Source

• types: add fallbackNS type handling 1975

v23.1.0

Compare Source

• cloneInstance: introduce forkResourceStore 1974
• types: default argument values for ParseKeys type

v23.0.2

Compare Source

• refactor: static createInstance for wider browser support 1973

v23.0.1

Compare Source

• types: export ParseKeys

v23.0.0

Compare Source

This is a major breaking release:

• redesigned TypeScript types 1911

• removed setDebug function in the logger: 1954

• changed returnNull default to false 1885

• drop support for old browsers and Node.js < v12 1948

• ordinal plural keys are now prefixed with _ordinal to help translators (non-breaking, because of fallback) 1945

➡️ check out the migration guide

v22.5.1

Compare Source

• ResourceStore addResource: offer possibility to pass keySeparator via options 1968

v22.5.0

Compare Source

• extend hasLoadedNamespace function options to pass optional lng to optimize server side usage of react-i18next

---

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

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @hugotomazi/capacitor-navigation-bar@2.0.1
npm ERR! Found: @capacitor/core@5.2.2
npm ERR! node_modules/@capacitor/core
npm ERR!   @capacitor/core@"^5.0.3" from the root project
npm ERR!   peer @capacitor/core@"^5.2.0" from @capacitor/android@5.2.2
npm ERR!   node_modules/@capacitor/android
npm ERR!     @capacitor/android@"^5.0.3" from the root project
npm ERR!   5 more (@capacitor/app, @capacitor/ios, @capacitor/network, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @capacitor/core@"^4.0.1" from @hugotomazi/capacitor-navigation-bar@2.0.1
npm ERR! node_modules/@hugotomazi/capacitor-navigation-bar
npm ERR!   @hugotomazi/capacitor-navigation-bar@"^2.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @capacitor/core@4.8.1
npm ERR! node_modules/@capacitor/core
npm ERR!   peer @capacitor/core@"^4.0.1" from @hugotomazi/capacitor-navigation-bar@2.0.1
npm ERR!   node_modules/@hugotomazi/capacitor-navigation-bar
npm ERR!     @hugotomazi/capacitor-navigation-bar@"^2.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/92b4d5/d5edc0/cache/others/npm/_logs/2023-07-21T13_59_23_364Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/92b4d5/d5edc0/cache/others/npm/_logs/2023-07-21T13_59_23_364Z-debug-0.log

[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.