chore: 🤖 update dependency i18next to v21.10.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
i18next (source)	21.6.16 → 21.10.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

i18next/i18next (i18next)

v21.10.0

Compare Source

• Add formatter cache 1843

v21.9.2

Compare Source

• optimize single quotes replacement for $t() nesting 1836

v21.9.1

Compare Source

• defaultNS can now also be set to false

v21.9.0

Compare Source

• Add Customizable Retry Logic 1810
• types: extend compatibilityJSON with v4

v21.8.16

Compare Source

• types: fix getDataByLanguage type 1810

v21.8.15

Compare Source

• fix: make sure retry logic ends for failed backend reads

v21.8.14

Compare Source

• allow overriding keyPrefix option t function returned from getFixedT (does not work for normal t function)

v21.8.13

Compare Source

• types: new optional unescape option for react-i18next

v21.8.12

Compare Source

• fix: respect pluralSeparator for special _zero handling

v21.8.11

Compare Source

• fix: types should always come first in exports 1796

v21.8.10

Compare Source

• types: fix loaded event result

v21.8.9

Compare Source

• fix: deepFind for null values 1790

v21.8.8

Compare Source

• fix: loadNamespaces() doesn't keep resolving order when the second request completes before the first one 1785

v21.8.7

Compare Source

• fix: allow formatters having '' for string options eg. this is an {{val, array(join: ' | ’)}}

v21.8.6

Compare Source

• fix: regression introduced in v21.6.11, respect appendNamespaceToMissingKey for parseMissingKeyHandler 1507

v21.8.5

Compare Source

• fix: interpolation with $ in values resets nextIndex to wrong position with skipOnVariables 1782

v21.8.4

Compare Source

• types: keyPrefix in react options

v21.8.3

Compare Source

• prevent chrome warnings because of window.navigator.userAgent usage 1778

v21.8.2

Compare Source

• types: add saveMissingPlurals option 1774

v21.8.1

Compare Source

• types: fix getDataByLanguage type 1810

v21.8.0

Compare Source

• add maxParallelReads option, default 10 1771
• reduce CPU usage loading large numbers of items 1768

v21.7.1

Compare Source

• types: missing returnDetails option in init options 1765

v21.7.0

Compare Source

• introduce returnDetails option 1764

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[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: pnpm-lock.yaml

(node:1638) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)