build(deps): update dependency react-i18next to v17.0.19 (#13504)

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [react-i18next](https://redirect.github.com/i18next/react-i18next) |
[`17.0.18` →
`17.0.19`](https://renovatebot.com/diffs/npm/react-i18next/17.0.18/17.0.19)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/react-i18next/17.0.19?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-i18next/17.0.18/17.0.19?slim=true)
|

---

### Release Notes

<details>
<summary>i18next/react-i18next (react-i18next)</summary>

###
[`v17.0.19`](https://redirect.github.com/i18next/react-i18next/blob/HEAD/CHANGELOG.md#17019)

[Compare
Source](https://redirect.github.com/i18next/react-i18next/compare/v17.0.18...v17.0.19)

- fix: `useTranslation` with an inline selector `keyPrefix`
(`useTranslation('ns', { keyPrefix: ($) => $.role })`) returned a new
`t` on every render, so every effect, `useCallback` and `useMemo`
depending on `t` ran again each time. The cached `t` was compared
against the `keyPrefix` function itself, and an inline arrow is a new
function on every render. It is now compared against the key the
selector resolves to (with the same options and namespace list
`getFixedT` resolves it with), so `t` keeps its identity as long as the
resolved prefix does, just like a string `keyPrefix`. A selector that
resolves to a different key still gets a new `t`, and i18next still
resolves the selector on each `t` call as before. Fixes
[#&#8203;1936](https://redirect.github.com/i18next/react-i18next/issues/1936).
- fix: `useTranslation` kept returning the previous `t` when only the
namespace (`useTranslation('a')` → `useTranslation('b')`) or only the
i18n instance (another instance with the same language, via props or
`I18nextProvider`) changed on a mounted component. That `t` kept
resolving against the old namespace or instance until something else
(the language, the ready state, a bound i18n event) produced a new one.
Both are now part of the check that decides whether the cached `t` can
be reused.

</details>

---

### Configuration

📅 **Schedule**: (UTC)

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/authelia/authelia).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE2NC4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImRlcGVuZGVuY2llcyIsImphdmFzY3JpcHQiXX0=-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

web/package.json

@@ -21,7 +21,7 @@
     "qrcode.react": "4.2.0",
     "react": "19.3.1",
     "react-dom": "19.3.1",
-    "react-i18next": "17.0.18",
+    "react-i18next": "17.0.19",
     "react-router": "8.4.0",
     "zxcvbn": "4.4.2"
   },

web/pnpm-lock.yaml

@@ -59,8 +59,8 @@ importers:
         specifier: 19.3.1
         version: 19.3.1(react@19.3.1)
       react-i18next:
-        specifier: 17.0.18
-        version: 17.0.18(@typescript/typescript6@6.0.2)(i18next@26.4.7(@typescript/typescript6@6.0.2))(react-dom@19.3.1(react@19.3.1))(react@19.3.1)
+        specifier: 17.0.19
+        version: 17.0.19(@typescript/typescript6@6.0.2)(i18next@26.4.7(@typescript/typescript6@6.0.2))(react-dom@19.3.1(react@19.3.1))(react@19.3.1)
       react-router:
         specifier: 8.4.0
         version: 8.4.0(react-dom@19.3.1(react@19.3.1))(react@19.3.1)
@@ -3365,8 +3365,8 @@ packages:
     peerDependencies:
       react: ^19.3.1
 
-  react-i18next@17.0.18:
-    resolution: {integrity: sha512-WC8i9i2QOom9q3v/aBzrGwUSbEBlvUylk2VV3k3kgUhMaAUyDZJ934PHfYJ2RUApzhG7cZCV0LlTVnVTLRjqcQ==}
+  react-i18next@17.0.19:
+    resolution: {integrity: sha512-BRHqiqOfW4J/LBVtbBFHoBoZm/Ez2/tkHPitYtn0CSpkYhEaEAsZMPsg7hZlomu30UJYQ6ZKiP3pwa3QnxGvQw==}
     peerDependencies:
       i18next: '>= 26.2.0'
       react: '>= 16.8.0'
@@ -7258,7 +7258,7 @@ snapshots:
       react: 19.3.1
       scheduler: 0.28.0
 
-  react-i18next@17.0.18(@typescript/typescript6@6.0.2)(i18next@26.4.7(@typescript/typescript6@6.0.2))(react-dom@19.3.1(react@19.3.1))(react@19.3.1):
+  react-i18next@17.0.19(@typescript/typescript6@6.0.2)(i18next@26.4.7(@typescript/typescript6@6.0.2))(react-dom@19.3.1(react@19.3.1))(react@19.3.1):
     dependencies:
       '@babel/runtime': 7.29.7
       html-parse-stringify: 4.0.1