i18n(ja): restore DM-master and DM-worker as literal English terms

[yahonda]

What is changed, added or deleted? (Required)

DM-master and DM-worker are the actual TiDB Data Migration (DM) tool component/binary names (matching the dm-master/dm-worker binaries and dm/master, dm/worker paths), not descriptive nouns that should be translated. This corpus rendered them inconsistently as katakana DMマスター/DMワーカー (and, found on a second pass, the space-separated variant DM マスター/DM ワーカー) in many places while other places already correctly kept them literal (DM-master/DM-worker).

This PR unifies all katakana occurrences (both spacing variants) to the literal English form, matching the direction already decided in a prior term-notation review.

• DMマスター / DM マスター → DM-master
• DMワーカー / DM ワーカー → DM-worker

101 files total, 465 sites (265 no-space + 200 space-separated, found on independent review of the first pass). Heading anchors ({#...}) were already stable English slugs, independent of the visible heading text, so none needed changing.

Generic uses of bare マスター/ワーカー (e.g. "master branch", other components) are unrelated to this term and were not touched — only the DM-prefixed forms were in scope.

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

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

[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