chore(deps): bump i18next-chained-backend from 4.6.2 to 5.0.6

[dependabot]

Bumps i18next-chained-backend from 4.6.2 to 5.0.6.

Changelog

Sourced from i18next-chained-backend's changelog.

5.0.6

• chore: removed the unused extend() helper from utils. It merged with for...in and no own-property check, so a source object carrying an own __proto__ key (as JSON.parse produces) reassigned the target's prototype. Nothing in the package called it and rollup already tree-shook it out of every published bundle, so this is a source cleanup with no effect on consumers.
• chore: defaults() now iterates own enumerable keys only and skips __proto__ / constructor / prototype. Its existing === undefined check already blocked the pollution paths, so this is defense in depth and aligns the helper with the equivalents in i18next-http-backend, i18next-fs-backend and i18next-http-middleware.

5.0.5

• fix: do not signal retry to i18next by default when all chained backends fail, introduce opt-in retryOnFailure option #53

5.0.4

• fix: signal retry to i18next when all chained backends fail #51

5.0.3

• warn when using saveMissing/updateMissing with multiple backends

5.0.2

• try to fix commonjs build to address #45

5.0.1

• try to adapt package export to address #44

5.0.0

• fix TS issue (needed to switch to ESM by default) #43

4.6.3

• Fix read-callback typing #39

Commits

• 586c5e2 5.0.6
• eefbca5 chore: remove unused extend() helper, guard defaults() against prototype keys
• aeae5e9 Bump @​babel/core from 7.29.0 to 7.29.6 (#55)
• 3e299b4 Bump js-yaml from 4.1.1 to 4.3.0 (#54)
• c0e38c4 5.0.5
• 6bf1cb6 fix: do not signal retry to i18next by default when all chained backends fail...
• 3c395c4 README: mention npx i18next-cli localize as the zero-to-localized path
• e213f03 Add Locize advice section near the top of README
• e4d31bc 5.0.4
• 5240cad release
• Additional commits viewable in compare view

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 commands and options

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)

[HughParry]

Superseded by #3281.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.