Localize UI frontend

[andypotato]

Description

This PR adds react-i18next UI localization infrastructure for both the web and image apps and moves existing user-facing strings into translation resources.

The change includes:

• i18n setup for apps/web and apps/image
• new English locale files grouped by feature/section
• wiring the app entry points to initialize localization
• updating dialogs, settings panels, welcome screens, and inspector sections to read strings from translations instead of hardcoded text

Motivation

The UI currently relies on hardcoded strings across many components, which makes future localization difficult and spreads copy changes throughout the codebase.

This change introduces a centralized translation layer so the project has a clean foundation for supporting additional languages later while also making UI copy easier to maintain.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Testing

• Tested locally
• Added/updated tests
• All tests passing

Tested by:

• verifying both apps/web and apps/image initialize with the new i18n setup
• checking translated strings render correctly in dialogs, settings, welcome flows, and inspector sections
• confirming existing UI behavior still works after replacing hardcoded labels with translation lookups

Checklist

• Code follows project style guidelines
• Self-review completed
• Comments added for complex code
• Documentation updated
• No console.log or debug code left
• Tests pass

[Augani]

Hey @andypotato — is this PR ready for review/merge? We'd like to evaluate it but want to make sure it's in a final state before we dig in. Let us know!