chore(deps): Bump i18next from 26.0.8 to 26.0.10 (#1876)

[//]: # (dependabot-start)
⚠️  **Dependabot is rebasing this PR** ⚠️ 

Rebasing might not happen immediately, so don't worry if this takes some
time.

Note: if you make any changes to this PR yourself, they will take
precedence over the rebase.

---

[//]: # (dependabot-end)

Bumps [i18next](https://github.com/i18next/i18next) from 26.0.8 to
26.0.10.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/i18next/i18next/releases">i18next's
releases</a>.</em></p>
<blockquote>
<h2>v26.0.10</h2>
<ul>
<li>feat: <code>getFixedT</code> accepts a fourth optional
<code>fixedOpts</code> argument carrying <code>scopeNs</code> — the full
namespace list the bound <code>t</code> was created for. The selector
API uses <code>scopeNs</code> to detect when a path's first segment is a
namespace prefix, <strong>without</strong> changing resolution scope.
Resolution still uses the bound <code>ns</code> (a single primary string
in the typical react-i18next setup), so plain <code>t('key')</code>
lookups stay isolated to the primary namespace exactly as before — only
<code>t($ =&gt; $.secondaryNs.foo)</code> selectors now route correctly
under <code>useTranslation([nsA, nsB])</code>. Fixes the runtime side of
<a
href="https://redirect.github.com/i18next/i18next/issues/2429">#2429</a>
for the <code>react-i18next</code> default-<code>nsMode</code> case. The
4th argument is opt-in: existing 3-arg <code>getFixedT(lng, ns,
keyPrefix)</code> callers see no behavior change.</li>
</ul>
<h2>v26.0.9</h2>
<ul>
<li>fix(types): unformatted interpolation values are now typed as
<code>string | number</code> (was <code>string</code>). i18next
stringifies values at runtime, so requiring callers to wrap numbers in
<code>String(...)</code> for plain <code>{{var}}</code> placeholders was
unnecessary friction — and could mask the real problem when a non-string
value was passed alongside multiple interpolation slots (the
<code>t()</code> overload resolution would fall through to the 3-arg
form and report a confusing &quot;not assignable to string&quot; error
against the options object). Typed format specifiers like <code>{{x,
number}}</code>, <code>{{x, currency}}</code>, <code>{{x,
datetime}}</code>, etc. keep their precise types; this only relaxes the
no-format default. The <code>count</code> variable remains
<code>number</code>-only</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/i18next/i18next/blob/master/CHANGELOG.md">i18next's
changelog</a>.</em></p>
<blockquote>
<h2>26.0.10</h2>
<ul>
<li>feat: <code>getFixedT</code> accepts a fourth optional
<code>fixedOpts</code> argument carrying <code>scopeNs</code> — the full
namespace list the bound <code>t</code> was created for. The selector
API uses <code>scopeNs</code> to detect when a path's first segment is a
namespace prefix, <strong>without</strong> changing resolution scope.
Resolution still uses the bound <code>ns</code> (a single primary string
in the typical react-i18next setup), so plain <code>t('key')</code>
lookups stay isolated to the primary namespace exactly as before — only
<code>t($ =&gt; $.secondaryNs.foo)</code> selectors now route correctly
under <code>useTranslation([nsA, nsB])</code>. Fixes the runtime side of
<a
href="https://redirect.github.com/i18next/i18next/issues/2429">#2429</a>
for the <code>react-i18next</code> default-<code>nsMode</code> case. The
4th argument is opt-in: existing 3-arg <code>getFixedT(lng, ns,
keyPrefix)</code> callers see no behavior change.</li>
</ul>
<h2>26.0.9</h2>
<ul>
<li>fix(types): unformatted interpolation values are now typed as
<code>string | number</code> (was <code>string</code>). i18next
stringifies values at runtime, so requiring callers to wrap numbers in
<code>String(...)</code> for plain <code>{{var}}</code> placeholders was
unnecessary friction — and could mask the real problem when a non-string
value was passed alongside multiple interpolation slots (the
<code>t()</code> overload resolution would fall through to the 3-arg
form and report a confusing &quot;not assignable to string&quot; error
against the options object). Typed format specifiers like <code>{{x,
number}}</code>, <code>{{x, currency}}</code>, <code>{{x,
datetime}}</code>, etc. keep their precise types; this only relaxes the
no-format default. The <code>count</code> variable remains
<code>number</code>-only</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="61eaf5be10"><code>61eaf5b</code></a>
26.0.10</li>
<li><a
href="47fd92f8aa"><code>47fd92f</code></a>
feat: getFixedT 4th-arg scopeNs decouples selector ns-detection from
resoluti...</li>
<li><a
href="caf33f6196"><code>caf33f6</code></a>
26.0.9</li>
<li><a
href="eed0146d95"><code>eed0146</code></a>
fix(types): relax unformatted interpolation values to <code>string |
number</code></li>
<li><a
href="170fb0a9e4"><code>170fb0a</code></a>
Modernize locize.com URLs and refresh UTM tags</li>
<li>See full diff in <a
href="https://github.com/i18next/i18next/compare/v26.0.8...v26.0.10">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=i18next&package-manager=npm_and_yarn&previous-version=26.0.8&new-version=26.0.10)](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 this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

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

package-lock.json

@@ -30,7 +30,7 @@
         "downshift": "^9.3.2",
         "events": "^3.3.0",
         "file-saver": "^2.0.5",
-        "i18next": "^26.0.8",
+        "i18next": "^26.0.10",
         "i18next-browser-languagedetector": "^8.2.1",
         "i18next-resources-to-backend": "^1.2.1",
         "json-stringify-pretty-compact": "^4.0.0",
@@ -8052,9 +8052,9 @@
       }
     },
     "node_modules/i18next": {
-      "version": "26.0.8",
-      "resolved": "https://registry.npmjs.org/i18next/-/i18next-26.0.8.tgz",
-      "integrity": "sha512-BRzLom0mhDhV9v0QhgUUHWQJuwFmnr1194xEcNLYD6ym8y8s542n4jXUvRLnhNTbh9PmpU6kGZamyuGHQMsGjw==",
+      "version": "26.0.10",
+      "resolved": "https://registry.npmjs.org/i18next/-/i18next-26.0.10.tgz",
+      "integrity": "sha512-k3yGPAlWR2RdMYoVXJoDZDT87qeHIWKH7gVksdZMpRty7QX/D9QZeYGvN08KGbKHke9wn01eYT+EEsrqX/YTlw==",
       "funding": [
         {
           "type": "individual",

package.json

@@ -47,7 +47,7 @@
     "downshift": "^9.3.2",
     "events": "^3.3.0",
     "file-saver": "^2.0.5",
-    "i18next": "^26.0.8",
+    "i18next": "^26.0.10",
     "i18next-browser-languagedetector": "^8.2.1",
     "i18next-resources-to-backend": "^1.2.1",
     "json-stringify-pretty-compact": "^4.0.0",