fix: swap officialVersion labels between en-US and zh-TW translations

[its-me]

What

The officialVersion translation strings in en-US.json and zh-TW.json are swapped:

File	Before (incorrect)	After (correct)
en-US.json	Version {version} (官方構建)	Version {version} (Official build)
zh-TW.json	版本 {version} (Official build)	版本 {version} (官方構建)

English-locale users see a Chinese string in the About dialog, and Traditional Chinese users see an English string — the labels were placed in the wrong locale files.

How to reproduce

Build AppFlowy with an English locale and open Settings → About AppFlowy. The version line shows Version x.y.z (官方構建) instead of Version x.y.z (Official build).

Summary by Sourcery

Bug Fixes:

• Fix swapped officialVersion translation strings between en-US and zh-TW so each locale displays the correct language label.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR corrects the officialVersion translation strings by swapping the English and Traditional Chinese labels into their proper locale files so that each locale shows the appropriate language in the About dialog.

File-Level Changes

Change	Details	Files
Fix mismatched officialVersion translation strings between English and Traditional Chinese locale files.	Update the officialVersion string in the English locale to use the English phrase Version {version} (Official build) Update the officialVersion string in the Traditional Chinese locale to use the Chinese phrase 版本 {version} (官方構建)	frontend/resources/translations/en-US.json frontend/resources/translations/zh-TW.json

---

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 - I've reviewed your changes and they look great!

---

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.}

[github-actions]

🥷 Ninja i18n – 🛎️ Translations need to be updated

Project /project.inlang

lint rule	new reports	level	link
Identical pattern	1	warning	contribute (via Fink 🐦)