chore(deps): Bump i18next from 25.10.10 to 26.0.1 (#1776)

Bumps [i18next](https://github.com/i18next/i18next) from 25.10.10 to
26.0.1.
<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.1</h2>
<ul>
<li>fix: Formatter no longer crashes when <code>alwaysFormat</code> is
<code>true</code> and no format specifier is present
(<code>format</code> is <code>undefined</code>)</li>
<li>fix: Formatter now returns <code>undefined</code>/<code>null</code>
values as-is instead of producing <code>NaN</code> when the value is
missing</li>
</ul>
<h2>v26.0.0</h2>
<p><strong>This is a major breaking release:</strong></p>
<h3>Breaking Changes</h3>
<ul>
<li><strong>Remove deprecated <code>initImmediate</code> option</strong>
— the backward-compatibility mapping from <code>initImmediate</code> to
<code>initAsync</code> (introduced in v24) has been removed. Use
<code>initAsync</code> instead.</li>
<li><strong>Remove legacy <code>interpolation.format</code>
function</strong> — the old monolithic format function
(<code>interpolation: { format: (value, format, lng) =&gt; ... }</code>)
is no longer supported. The built-in Formatter (or a custom Formatter
module via <code>.use()</code>) is now always used. Migrate to the <a
href="https://www.i18next.com/translation-function/formatting">new
formatting approach</a> using
<code>i18next.services.formatter.add()</code> or
<code>.addCached()</code> for custom formatters.</li>
<li><strong>Remove console support notice</strong> — the console support
notice introduced in v25.8.0 has been removed, along with the
<code>showSupportNotice</code> option and all related internal
suppression logic (<code>globalThis.__i18next_supportNoticeShown</code>,
<code>I18NEXT_NO_SUPPORT_NOTICE</code> env var). See our blog post for
the <a href="https://www.locize.com/blog/i18next-support-notice">full
story</a>.</li>
<li><strong>Remove <code>simplifyPluralSuffix</code> option</strong> —
this option was unused by the core PluralResolver (which relies entirely
on <code>Intl.PluralRules</code>). It only had an effect in the old
v1/v2/v3 compatibility layer. The v4 test compatibility layer now
defaults to <code>true</code> internally.</li>
<li><strong>Remove deprecated <code>@babel/polyfill</code></strong> from
devDependencies.</li>
</ul>
<h3>Improvements</h3>
<ul>
<li><strong>Code modernization</strong> across all source files:
<ul>
<li>Replace <code>indexOf() &gt; -1</code> / <code>indexOf() &lt;
0</code> with <code>.includes()</code> (~40+ occurrences)</li>
<li>Replace <code>indexOf() === 0</code> with <code>.startsWith()</code>
where appropriate</li>
<li>Replace <code>var</code> with <code>const</code>, <code>'' +
object</code> with <code>String(object)</code>,
<code>.substring()</code> with <code>.slice()</code></li>
<li>Replace <code>.apply(observer, [event, ...args])</code> with direct
call <code>observer(event, ...args)</code></li>
<li>Remove unnecessary <code>.call(this, ...)</code> in BackendConnector
retry logic</li>
<li>Fix <code>array-callback-return</code> in LanguageUtils
<code>getBestMatchFromCodes</code></li>
<li>Clean up all stale <code>eslint-disable</code> comments from source
files</li>
</ul>
</li>
<li><strong>EventEmitter</strong>: add <code>once()</code> method for
one-time event subscriptions</li>
<li><strong>Memory leak fix</strong>: move module-level
<code>checkedLoadedFor</code> cache to Translator instance, preventing
cross-instance state leakage</li>
<li><strong>TypeScript</strong>: fix <code>BackendModule</code> generic
parameter naming inconsistency between CJS and ESM type definitions</li>
<li><strong>TypeScript</strong>: add <code>once()</code> method to
<code>i18n</code> and <code>ResourceStore</code> type interfaces</li>
<li><strong>ESLint 9</strong>: migrate from ESLint 8 (airbnb-base) to
ESLint 9 flat config with <a
href="https://github.com/neostandard/neostandard">neostandard</a></li>
<li><strong>Vitest 4</strong>: upgrade from vitest 3 to vitest 4,
migrate workspace files to <code>test.projects</code> config</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.1</h2>
<ul>
<li>fix: Formatter no longer crashes when <code>alwaysFormat</code> is
<code>true</code> and no format specifier is present
(<code>format</code> is <code>undefined</code>)</li>
<li>fix: Formatter now returns <code>undefined</code>/<code>null</code>
values as-is instead of producing <code>NaN</code> when the value is
missing</li>
</ul>
<h2>26.0.0</h2>
<p><strong>This is a major breaking release:</strong></p>
<h3>Breaking Changes</h3>
<ul>
<li><strong>Remove deprecated <code>initImmediate</code> option</strong>
— the backward-compatibility mapping from <code>initImmediate</code> to
<code>initAsync</code> (introduced in v24) has been removed. Use
<code>initAsync</code> instead.</li>
<li><strong>Remove legacy <code>interpolation.format</code>
function</strong> — the old monolithic format function
(<code>interpolation: { format: (value, format, lng) =&gt; ... }</code>)
is no longer supported. The built-in Formatter (or a custom Formatter
module via <code>.use()</code>) is now always used. Migrate to the <a
href="https://www.i18next.com/translation-function/formatting">new
formatting approach</a> using
<code>i18next.services.formatter.add()</code> or
<code>.addCached()</code> for custom formatters.</li>
<li><strong>Remove console support notice</strong> — the console support
notice introduced in v25.8.0 has been removed, along with the
<code>showSupportNotice</code> option and all related internal
suppression logic (<code>globalThis.__i18next_supportNoticeShown</code>,
<code>I18NEXT_NO_SUPPORT_NOTICE</code> env var). See our blog post for
the <a href="https://www.locize.com/blog/i18next-support-notice">full
story</a>.</li>
<li><strong>Remove <code>simplifyPluralSuffix</code> option</strong> —
this option was unused by the core PluralResolver (which relies entirely
on <code>Intl.PluralRules</code>). It only had an effect in the old
v1/v2/v3 compatibility layer. The v4 test compatibility layer now
defaults to <code>true</code> internally.</li>
<li><strong>Remove deprecated <code>@babel/polyfill</code></strong> from
devDependencies.</li>
</ul>
<h3>Improvements</h3>
<ul>
<li><strong>Code modernization</strong> across all source files:
<ul>
<li>Replace <code>indexOf() &gt; -1</code> / <code>indexOf() &lt;
0</code> with <code>.includes()</code> (~40+ occurrences)</li>
<li>Replace <code>indexOf() === 0</code> with <code>.startsWith()</code>
where appropriate</li>
<li>Replace <code>var</code> with <code>const</code>, <code>'' +
object</code> with <code>String(object)</code>,
<code>.substring()</code> with <code>.slice()</code></li>
<li>Replace <code>.apply(observer, [event, ...args])</code> with direct
call <code>observer(event, ...args)</code></li>
<li>Remove unnecessary <code>.call(this, ...)</code> in BackendConnector
retry logic</li>
<li>Fix <code>array-callback-return</code> in LanguageUtils
<code>getBestMatchFromCodes</code></li>
<li>Clean up all stale <code>eslint-disable</code> comments from source
files</li>
</ul>
</li>
<li><strong>EventEmitter</strong>: add <code>once()</code> method for
one-time event subscriptions</li>
<li><strong>Memory leak fix</strong>: move module-level
<code>checkedLoadedFor</code> cache to Translator instance, preventing
cross-instance state leakage</li>
<li><strong>TypeScript</strong>: fix <code>BackendModule</code> generic
parameter naming inconsistency between CJS and ESM type definitions</li>
<li><strong>TypeScript</strong>: add <code>once()</code> method to
<code>i18n</code> and <code>ResourceStore</code> type interfaces</li>
<li><strong>ESLint 9</strong>: migrate from ESLint 8 (airbnb-base) to
ESLint 9 flat config with <a
href="https://github.com/neostandard/neostandard">neostandard</a></li>
<li><strong>Vitest 4</strong>: upgrade from vitest 3 to vitest 4,
migrate workspace files to <code>test.projects</code> config</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="18b3dbb473"><code>18b3dbb</code></a>
26.0.1</li>
<li><a
href="c829f91a2a"><code>c829f91</code></a>
fix: Formater crashes etc.</li>
<li><a
href="1593d1125e"><code>1593d11</code></a>
remove node v18 from github actions</li>
<li><a
href="d85c23da86"><code>d85c23d</code></a>
26.0.0</li>
<li><a
href="fad19d59cf"><code>fad19d5</code></a>
feat!: v26.0.0 — major version with breaking changes</li>
<li><a
href="780aa9170f"><code>780aa91</code></a>
jsr update</li>
<li>See full diff in <a
href="https://github.com/i18next/i18next/compare/v25.10.10...v26.0.1">compare
view</a></li>
</ul>
</details>
<br />

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

package.json

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