feat(i18n): implement internationalization framework and spanish tran…

[Luchi5544]

closes #70

Description

This PR integrates a robust internationalization framework into the Wraith Protocol Demo app using react-i18next and i18next-browser-languagedetector. It extracts all hardcoded user-visible text into translation dictionaries, introduces a locale switcher in the header, and implements persistent preferences.

Key Changes

• Framework Initialization: Set up react-i18next with browser language detection (src/i18n/index.ts).
• Locale Switcher Component: Created LocaleSwitcher (src/components/LocaleSwitcher.tsx) that changes languages via react-i18next and persists the selection in localStorage under the key wraith-locale.
• UI Integration: Added the LocaleSwitcher dropdown to the header right next to the chain switcher.
• String Extraction: Replaced all user-visible strings inside components (e.g. CkbReceive, CkbSend, SolanaReceive, SolanaSend, StellarReceive, StellarSend, HorizenReceive, HorizenSend, WalletConnect, etc.) with t() function hooks.
• Dictionaries:
  • src/i18n/en.json: All original English strings.
  • src/i18n/es.json: Full Spanish translations matching all keys.
• Dependency Configuration: Added a local pnpm-workspace.yaml and .npmrc to ensure node-gyp packages (like keccak, secp256k1, esbuild) can build non-interactively in standard CI/CD and developer environments.

Verification Results

• Ran npx pnpm format to format code style constraints.
• Ran npx pnpm run build which successfully ran type checking tsc --noEmit and Vite production bundling with 0 warnings or errors.

[vercel]

@Luchi5544 is attempting to deploy a commit to the truthixify's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@Luchi5544 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[truthixify]

i18n scaffolding + Spanish locale + LocaleSwitcher + instrumenting all chain components looks right. 5 conflicts to resolve:

git fetch origin
git rebase origin/develop
git push --force-with-lease

For each conflicted file, keep develop's structure (it has more recent work) and re-apply your t() call replacements on top. The i18n config and the JSON files land clean.

[truthixify]

The i18n work itself is good, but now after #87 just landed (push notifications, modified StellarReceive.tsx), this PR conflicts in src/components/StellarReceive.tsx. Plus develop has had other StellarReceive updates while this PR was open.

git fetch origin
git rebase origin/develop
git push --force-with-lease

When resolving, keep develop's StellarReceive structure and re-apply your t() call replacements on top. The i18n config files (en.json, es.json, index.ts) land clean.

[truthixify]

#92 just landed (WalletConnect v2) which added deps to pnpm-lock.yaml. Quick rebase:

git fetch origin
git rebase origin/develop
# pnpm-lock.yaml: easiest is to take develop's version then re-run `pnpm install` to add your own deps back
pnpm install
git add pnpm-lock.yaml
# also resolve any src/components/WalletConnect.tsx conflict — keep develop's WalletConnect integration
git rebase --continue
git push --force-with-lease

[truthixify]

Conflicts in package.json, pnpm-lock.yaml, and StellarReceive.tsx after #91 landed (QR support added a QR button to the receive flow).

git fetch origin
git rebase origin/develop
# package.json: keep both sets of deps
pnpm install  # regenerates lockfile
# StellarReceive.tsx: keep develop's QR integration, then re-apply your t() call wrappings
git add -u
git rebase --continue
git push --force-with-lease