chore(deps): Bump react-i18next from 17.0.19 to 17.0.21 in the react group (#2251)

Bumps the react group with 1 update:
[react-i18next](https://github.com/i18next/react-i18next).

Updates `react-i18next` from 17.0.19 to 17.0.21
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md">react-i18next's
changelog</a>.</em></p>
<blockquote>
<h2>17.0.21</h2>
<ul>
<li>fix(IcuTrans): explicit <code>values</code> now win over
<code>interpolation.defaultVariables</code>, as they do in
<code>t()</code>. <code>IcuTrans</code> merged them the other way round,
so <code>&lt;IcuTrans values={{ user: 'John Doe' }} /&gt;</code>
rendered the configured default variable <code>user</code> instead of
<code>John Doe</code>. <code>Trans</code> had the same inverted merge
and is fixed too. Compatibility note: only names that are set both in
<code>values</code> and in <code>defaultVariables</code> render
differently.</li>
<li>feat: new entry point
<code>react-i18next/IcuTransWithoutContext</code> (with types) for React
Server Components. Importing <code>IcuTransWithoutContext</code> from
<code>react-i18next</code> in a Server Component could fail the build
with <code>createContext is not a function</code>, because the main
entry creates the React context when it is loaded. Like
<code>react-i18next/TransWithoutContext</code>, the new entry point does
not.</li>
<li>fix(build): the ESM build's <code>dist/es/package.json</code> now
declares <code>&quot;sideEffects&quot;: false</code>, like the root
<code>package.json</code> already did. Bundlers use the nearest
<code>package.json</code>, so the ESM build counted as having side
effects and unused exports were kept: an app that only uses
<code>Trans</code> still bundled <code>IcuTrans</code> with its HTML
entity decoder, <code>useTranslation</code> and
<code>use-sync-external-store</code>. With esbuild, a
<code>Trans</code>-only bundle (React and i18next external) goes from
20.9 KB to 11.6 KB minified, 8.3 KB to 5.0 KB gzipped.</li>
<li>docs: the <code>icu.macro</code> Babel macro is now marked as
deprecated in favour of using <code>IcuTrans</code> directly. It fails
on Babel 8 (<code>t.jSXIdentifier is not a function</code>),
<code>&lt;Plural count={count}&gt;</code> renders the raw ICU message,
and a React <code>key</code> on
<code>&lt;Plural&gt;</code>/<code>&lt;Select&gt;</code> becomes an ICU
case. It keeps working on Babel 7 and is not removed. The
<code>IcuTrans</code> docs page has a corrected example and props table
and covers Server Components.</li>
</ul>
<h2>17.0.20</h2>
<ul>
<li>fix: <code>useTranslation</code> no longer suspends when a missing
namespace is loaded by a synchronous backend. With
<code>useSuspense</code> (the default), a namespace that wasn't in the
store yet always made the component throw the loading promise, even when
the backend had already delivered the resources while that promise was
being created. React then showed the <code>Suspense</code> fallback and
rendered again right away, which appears as a fallback flash (a white
flash in React Native) and costs performance. The hook now starts the
load first, checks the store again and only suspends if the namespace is
still missing. This helps every backend that calls back synchronously,
for example <code>i18next-resources-to-backend</code> with a static
resources object or a loader that returns the data directly. Async
backends, and an instance that isn't initialized yet, still suspend as
before. Thanks <a
href="https://github.com/oblador"><code>@​oblador</code></a> (<a
href="https://redirect.github.com/i18next/react-i18next/pull/1937">#1937</a>).</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/i18next/react-i18next/commit/64a3d1360fd0bf2f49652c09881be04a5e22082f"><code>64a3d13</code></a>
17.0.21</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/c7e1c80f066abb68dc1399e3a069e0a5b7dddaa8"><code>c7e1c80</code></a>
fix(IcuTrans): explicit values win over defaultVariables, RSC entry
point, ES...</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/66dbfbab1c5430a99a7d9badc308f59fa3931678"><code>66dbfba</code></a>
17.0.20</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/806df1ee326534bd1656fcc88239321f70c9c65f"><code>806df1e</code></a>
build, changelog for 17.0.20</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/49ec36d359236d3f5f7298b9da355754eb1fb719"><code>49ec36d</code></a>
fix(useTranslation): don't suspend synchronous backends (<a
href="https://redirect.github.com/i18next/react-i18next/issues/1937">#1937</a>)</li>
<li>See full diff in <a
href="https://github.com/i18next/react-i18next/compare/v17.0.19...v17.0.21">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=react-i18next&package-manager=npm_and_yarn&previous-version=17.0.19&new-version=17.0.21)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

package-lock.json

@@ -55,7 +55,7 @@
         "react-collapse": "^5.1.1",
         "react-color": "^2.19.3",
         "react-dom": "^19.3.1",
-        "react-i18next": "^17.0.19",
+        "react-i18next": "^17.0.21",
         "react-icons": "^5.7.0",
         "react-markdown": "^10.1.0",
         "react-resizable-panels": "^4.14.5",
@@ -10684,9 +10684,9 @@
       }
     },
     "node_modules/react-i18next": {
-      "version": "17.0.19",
-      "resolved": "https://registry.npmjs.org/react-i18next/-/react-i18next-17.0.19.tgz",
-      "integrity": "sha512-BRHqiqOfW4J/LBVtbBFHoBoZm/Ez2/tkHPitYtn0CSpkYhEaEAsZMPsg7hZlomu30UJYQ6ZKiP3pwa3QnxGvQw==",
+      "version": "17.0.21",
+      "resolved": "https://registry.npmjs.org/react-i18next/-/react-i18next-17.0.21.tgz",
+      "integrity": "sha512-bcOTaZQKsNb4KKIc+T6Dx1Cf0x3UTV5io8X1PyaC38oOeNEbU5CNkW+5QmOGEyDSEbK/QC2kLXOgL9zeCIxR3g==",
       "license": "MIT",
       "dependencies": {
         "@babel/runtime": "^7.29.7",