i18n(ja): fix scrambled issue/author links in release notes

[yahonda]

What is changed, added or deleted? (Required)

Machine translation scrambled many release-note bullets so that the issue/PR links [#NNNN](...) and author attribution links @[handle](...) landed in the middle of the sentence instead of at the end (where the English source and the site convention place them). This left ungrammatical Japanese and misplaced author credits, and in several cases the author handle was rendered with a stray space (@ [handle]) or transliterated into katakana.

This PR, matching the English source line-by-line, for each affected bullet:

• moves the [#NNNN] / @[handle] link cluster to the end of the bullet in English word order;
• repairs the particle at the former link site so the Japanese reads naturally;
• normalizes @ [handle] → @[handle] on the touched lines;
• restores transliterated author handles to the English display (e.g. チャールズ・チュン96 → CharlesCheung96, ハイ・ラスティン → hi-rustin).

Scope: 99 scrambled bullets across 32 releases/*.md files. Only mid-sentence-scrambled bullets are touched.

Intentionally out of scope (separate cleanup):

• Full-width issue-ref markers ＃ are left exactly as-is (count unchanged: 8954).
• Author links that were already at end-of-line but carry the @ [handle] spacing artifact (~3200 across release notes) are a separate mechanical PR.

Note: this touches a few lines in release-6.1.6.md that PR #23408 (execution-plan term) also edits on the same lines; whichever merges first, the other will be rebased (the two changes combine cleanly).

Which TiDB version(s) do your changes apply to? (Required)

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

N/A

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lilin90 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8afb969c-ac09-4823-878a-d2898d34eba5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-08-04 02:50:18.330378023 +0000 UTC m=+2496404.366473079: ☑️ agreed by qiancai.