Update dependency i18next to v23.7.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
i18next (source)	23.5.1 -> 23.7.6

---

Release Notes

i18next/i18next (i18next)

v23.7.6

Compare Source

• types: CustomInstanceExtenstions

v23.7.5

Compare Source

• fix types export for TypeScript v4 in combination with react-i18next

v23.7.4

Compare Source

• fix for TypeScript v4 in combination with react-i18next

v23.7.3

Compare Source

• fix: consider importing '*.js'

v23.7.2

Compare Source

• types: optimize mts

v23.7.1

Compare Source

• fix some mjs typings

v23.7.0

Compare Source

• fix: separate cjs and mjs typings 2010
• fix: consider importing './typescript/t.js' 2048

v23.6.0

Compare Source

• add interpolation data to response if returnDetails is true 2053

---

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

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @badeball/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/cypress
npm ERR!   cypress@"^13.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer cypress@"^10.0.0 || ^11.0.0 || ^12.0.0" from @badeball/[email protected]
npm ERR! node_modules/@badeball/cypress-cucumber-preprocessor
npm ERR!   @badeball/cypress-cucumber-preprocessor@"^18.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/cypress
npm ERR!   peer cypress@"^10.0.0 || ^11.0.0 || ^12.0.0" from @badeball/[email protected]
npm ERR!   node_modules/@badeball/cypress-cucumber-preprocessor
npm ERR!     @badeball/cypress-cucumber-preprocessor@"^18.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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/417778/1ab2dd/cache/others/npm/_logs/2023-11-13T12_47_08_715Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/417778/1ab2dd/cache/others/npm/_logs/2023-11-13T12_47_08_715Z-debug-0.log

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication