chore(deps): Bump react-i18next from 17.1.4 to 17.1.8 in the react group (#2271)

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

Updates `react-i18next` from 17.1.4 to 17.1.8
<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.1.8</h2>
<ul>
<li>fix(Trans): an interpolation variable named <code>format</code> is
no longer dropped. <code>Trans</code> reads <code>format</code> in an
interpolation object as the formatter name (<code>{{ value, format
}}</code>), so with <code>{{ format }}</code> as the only key nothing
was left: <code>&lt;Trans&gt;Export as {{ format }}&lt;/Trans&gt;</code>
warned <code>TRANS_INVALID_OBJ</code> and used the default string
<code>Export as </code> instead of <code>Export as {{format}}</code>.
When <code>format</code> is the object's only key it is now treated as
the variable. <code>{{ value, format }}</code> works as before. Without
an <code>i18nKey</code>, the key derived from the children changes
accordingly, from <code>Export as </code> to <code>Export as
{{format}}</code>. i18next-cli serializes <code>Trans</code> children
with react-i18next, so extracting with this version produces the same
key. Thanks <a
href="https://github.com/Pharex38"><code>@​Pharex38</code></a> (<a
href="https://redirect.github.com/i18next/react-i18next/pull/1944">#1944</a>).</li>
</ul>
<h2>17.1.7</h2>
<ul>
<li>fix(IcuTrans): each HTML entity in a translation is now decoded
exactly once. Named, decimal and hexadecimal entities were decoded in
three passes, and each pass decoded the output of the previous one, so
an escaped numeric entity was decoded twice: <code>&quot;Write
&amp;amp;[#169](https://github.com/i18next/react-i18next/issues/169); to
get
&amp;[#169](https://github.com/i18next/react-i18next/issues/169);&quot;</code>
rendered <code>Write © to get ©</code> instead of <code>Write
&amp;[#169](https://github.com/i18next/react-i18next/issues/169); to get
©</code>, and
<code>&amp;amp;[#60](https://github.com/i18next/react-i18next/issues/60);</code>
rendered <code>&lt;</code> instead of
<code>&amp;[#60](https://github.com/i18next/react-i18next/issues/60);</code>.
This also hit interpolated values with <code>escapeValue: true</code>,
where a value containing
<code>&amp;[#60](https://github.com/i18next/react-i18next/issues/60);</code>
is escaped to
<code>&amp;amp;[#60](https://github.com/i18next/react-i18next/issues/60);</code>.
Escaped named entities like <code>&amp;amp;lt;</code> already stayed
<code>&amp;lt;</code>, as browsers and <code>Trans</code> decode them.
Unknown named entities and entities above U+10FFFF still stay as
written. Thanks <a
href="https://github.com/Pharex38"><code>@​Pharex38</code></a> (<a
href="https://redirect.github.com/i18next/react-i18next/pull/1943">#1943</a>).</li>
</ul>
<h2>17.1.6</h2>
<ul>
<li>fix(Trans): a <code>count</code> passed in <code>tOptions</code> is
now used. <code>Trans</code> spread <code>tOptions</code> and then set
its own <code>count</code> prop, so a count only in
<code>tOptions</code> was overwritten with <code>undefined</code>:
<code>&lt;Trans i18nKey=&quot;items&quot; tOptions={{ count: 5 }}
/&gt;</code> rendered the key <code>items</code> instead of <code>5
items</code>, and with children <code>Trans</code> could pick the wrong
plural form. Like <code>context</code>, <code>Trans</code> now falls
back to <code>tOptions.count</code>, handled the same way as the
<code>count</code> prop. A <code>count</code> prop, a count in the
children or <code>values.count</code> still take precedence, and
<code>tOptions</code> is not modified. Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/react-i18next/pull/1942">#1942</a>).</li>
</ul>
<h2>17.1.5</h2>
<ul>
<li>fix(Trans): with an array of keys and no children,
<code>Trans</code> now falls back to the last key when none of them has
a translation, as <code>t()</code> does. It used the array itself as
<code>defaultValue</code>, which i18next handles as an object, so
<code>&lt;Trans i18nKey={['notifications.crm_item_created',
'crm_item_created']} components={[&lt;strong /&gt;]} /&gt;</code>
rendered <code>key 'crm_item_created (en)' returned an object instead of
string.</code> instead of <code>crm_item_created</code>. An array of
selectors falls back to the key of the last selector. The first key that
has a translation still wins, and <code>children</code>,
<code>defaults</code> and <code>tOptions.defaultValue</code> are used as
before. With <code>saveMissing</code>, these calls now report the
missing key, like a single <code>i18nKey</code> does. Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/react-i18next/pull/1941">#1941</a>).</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/i18next/react-i18next/commit/3f0880e218f7d1235f474faf1d695d0fbde94a48"><code>3f0880e</code></a>
17.1.8</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/9802f17e3921028ec2f582284b8dc344d4cd8f4d"><code>9802f17</code></a>
build</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/fb5fa17ea9be7b6bcc9990064f99aacb81eaa753"><code>fb5fa17</code></a>
changelog for 17.1.8</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/63f4e41dda4cb42e03edde5611f44018620bdc62"><code>63f4e41</code></a>
fix(Trans): don't drop an interpolation variable named format (<a
href="https://redirect.github.com/i18next/react-i18next/issues/1944">#1944</a>)</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/8655c0f679d4ec8002a2db1c5ad4d447a973d115"><code>8655c0f</code></a>
17.1.7</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/5e2cf4ac622c282572bce4a4cfef1324fb763365"><code>5e2cf4a</code></a>
build</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/4745dc626e14b55095e5f7ac5684859de6dfcd9b"><code>4745dc6</code></a>
changelog for 17.1.7</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/b708a76aedb44484b4fde924ad9e1630adfcbcc1"><code>b708a76</code></a>
fix(IcuTrans): decode each HTML entity only once (<a
href="https://redirect.github.com/i18next/react-i18next/issues/1943">#1943</a>)</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/a8626e0470cdb627a6af420c67ac03a59ae9aff8"><code>a8626e0</code></a>
17.1.6</li>
<li><a
href="https://github.com/i18next/react-i18next/commit/c0cafdf3f4a8b174e05ea999de0b4fe1fb55ec91"><code>c0cafdf</code></a>
build</li>
<li>Additional commits viewable in <a
href="https://github.com/i18next/react-i18next/compare/v17.1.4...v17.1.8">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.1.4&new-version=17.1.8)](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.1.4",
+        "react-i18next": "^17.1.8",
         "react-icons": "^5.7.0",
         "react-markdown": "^10.1.0",
         "react-resizable-panels": "^4.14.8",

package.json

@@ -73,7 +73,7 @@
     "react-collapse": "^5.1.1",
     "react-color": "^2.19.3",
     "react-dom": "^19.3.1",
-    "react-i18next": "^17.1.4",
+    "react-i18next": "^17.1.8",
     "react-icons": "^5.7.0",
     "react-markdown": "^10.1.0",
     "react-resizable-panels": "^4.14.8",