fix: resolve Weblate integration issues with translation key inconsistencies

[Anshumancanrock]

📌 Fixes

Fixes #240

---

📝 Summary of Changes

• Fixed translation key inconsistencies that were causing Weblate merge conflicts
• Removed extra homeButtonTitle key from 11 non-English locale files (de, es, fr, hi, id, ja, pt_BR, ru, vi, zh_CN, zh_TW)
• Added 20 missing translation keys to Portuguese locale file to match English reference
• Ensured all 12 locale files now have exactly 64 translation keys, consistent with English
• No duplicate Chinese files found

---

📸 Screenshots / Demo (if UI-related)

---

✅ Checklist

• I’ve tested my changes locally
• I’ve added tests (if applicable)
• I’ve updated documentation (if applicable)
• My code follows the project’s code style guidelines

---

👀 Reviewer Notes

Summary by Sourcery

Fix translation key inconsistencies and align all locale files with the English reference to resolve Weblate integration issues

Bug Fixes:

• Resolve Weblate merge conflicts by correcting translation key discrepancies across locale files

Enhancements:

• Remove extra homeButtonTitle key from 11 non-English locales
• Add 20 missing translation keys to the Portuguese locale file
• Ensure all 12 locale files have exactly 64 keys matching the English reference

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Consider adding a CI check or script to automatically validate that all locale files match the reference keys to prevent future merge conflicts.
• It would help to sort the keys alphabetically in each messages.json so that diffs are cleaner and easier to review.
• You may want to have a native Portuguese speaker review the newly added translations to ensure accuracy and context.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider adding a CI check or script to automatically validate that all locale files match the reference keys to prevent future merge conflicts.
- It would help to sort the keys alphabetically in each messages.json so that diffs are cleaner and easier to review.
- You may want to have a native Portuguese speaker review the newly added translations to ensure accuracy and context.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Anshumancanrock]

@vedansh-5 Please review this PR and let me know if you want any changes. Thanks !

[vedansh-5]

@Anshumancanrock Please add screenshots of the translation in any of the languages of all the possible screens.