chore: sync react native localization from platform-localization

[platform-localization-pr-bot]

Automated localization sync from platform-localization.

• Platform: React Native
• Source ref: 08557a1b740fd7dcd43ccc2cf3527a552a8d0ee5
• Workflow: Distribute React Native Localization

Greptile Summary

This PR syncs two additional native translation catalogs from platform-localization. The main changes are:

• Adds Afrikaans translations for all current native keys.
• Adds Swedish translations for all current native keys.

Confidence Score: 4/5

Afrikaans and Swedish remain unreachable until the SDK locale registry includes them.

• Both catalogs match the current English key set.
• locales/index.ts does not import or register either locale.
• Device and explicit af or sv locale values therefore fall back to English.

packages/ui/src/i18n/locales/index.ts

Important Files Changed

Filename	Overview
packages/ui/src/i18n/locales/af.json	Adds a complete Afrikaans catalog, but it is not registered in the SDK locale resources.
packages/ui/src/i18n/locales/sv.json	Adds a complete Swedish catalog, but it is not registered in the SDK locale resources.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
packages/ui/src/i18n/locales/af.json:1
**New Locales Remain Unregistered**

When the device or provider locale is `af`, `af-*`, `sv`, or `sv-*`, the hardcoded resource registry does not recognize either new catalog and falls back to English. Both files need corresponding imports and entries in `locales/index.ts` so their translations become reachable.

_{Reviews (1): Last reviewed commit: "chore: sync react native localization" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used (10)

• Rule used - Translation JSON under packages/ui/src/i18n/locale... (source)
• Context used - AGENTS.md (source)
• Context used - CLAUDE.md (source)
• File used - docs/contributing/native-i18n.md (source)
• File used - packages/ui/src/i18n/locales/en.json (source)
• File used - packages/ui/src/i18n/locales/es.json (source)
• File used - packages/ui/src/i18n/locales/index.ts (source)
• File used - docs/adr/0008-sdk-owned-i18next-no-consumer-overrides.md (source)
• File used - docs/adr/0009-deferred-dom-localization.md (source)
• File used - docs/adr/0007-app-locale-vs-bible-language-id.md (source)

[greptile-apps]

New Locales Remain Unregistered

When the device or provider locale is af, af-*, sv, or sv-*, the hardcoded resource registry does not recognize either new catalog and falls back to English. Both files need corresponding imports and entries in locales/index.ts so their translations become reachable.

Rule Used: Translation JSON under packages/ui/src/i18n/locale... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/ui/src/i18n/locales/af.json
Line: 1

Comment:
**New Locales Remain Unregistered**

When the device or provider locale is `af`, `af-*`, `sv`, or `sv-*`, the hardcoded resource registry does not recognize either new catalog and falls back to English. Both files need corresponding imports and entries in `locales/index.ts` so their translations become reachable.

**Rule Used:** Translation JSON under packages/ui/src/i18n/locale... ([source](.greptile))

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!