i18n(ja): unify deployment topology term notation

[yahonda]

What is changed, added or deleted? (Required)

Unifies 3 competing renderings of "deployment topology" (展開トポロジー/デプロイトポロジー/デプロイメントトポロジー) to 展開トポロジ, matching the actual title/H1 already used by the two pages this term most often refers to or links to (hybrid-deployment-topology.md, geo-distributed-deployment-topology.md — both titled "...展開トポロジ" with no long vowel mark).

production-deployment-using-tiup.md had both 展開トポロジー and デプロイメントトポロジー within the same file — a same-file self-contradiction.

6 files, 9 sites.

Found while investigating a broader "deployment" (展開/デプロイ/配置) notation question — the bare terms occur tens of thousands of times across the corpus for many unrelated meanings (UI "expand", generic "arrangement", etc.), so a full sweep isn't practical, but this specific "deployment topology" compound term was a small, clearly-scoped, and clearly-inconsistent subset.

Verified markdownlint-cli2 clean on all touched files.

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

• i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

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

• This PR is translated from:
• Other reference link(s):

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[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 overvenus 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

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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

[yahonda]

Consolidated into #23647, which now includes this PR's deployment-topology term fix along with the broader deploy/deployment sweep.