i18n(ja): align heading anchors with the English source

[yahonda]

What is changed, added or deleted? (Required)

Align the Japanese heading {#anchor} slugs with the English source across 123 files, so that intra-document anchor links resolve correctly.

The machine-translation pipeline had regenerated many anchors from the Japanese heading text (or mangled them), leaving them out of sync with the English GitHub-generated slugs that the intra-doc links rely on. This PR restores each heading anchor to the English slug, following GitHub's slug rules:

• Underscores are kept (e.g. `EMBED_TEXT()` → {#embed_text}, not {#embed-text}).
• + and dots collapse per GitHub (e.g. "Auto-embedding + Vector Index" → {#auto-embedding--vector-index}; "before TiDB v6.6.0" → {#...-v660}).
• Duplicate headings keep their -1 / -2 disambiguation suffixes.
• Angle-bracket placeholders inside code spans are preserved (e.g. `region <region_id> [--jq="<query string>"]` → {#region-region_id---jqquery-string}).

Verification:

• All 925 changed anchors were checked against the English GitHub slugs — all match.
• Broken intra-document anchor links across these files dropped from 188 (before) to 0 (after).

Also included (same heading line, so kept in this PR to avoid a conflicting edit):

• br/backup-and-restore-overview.md: the section heading "TiDB v6.6.0以前…" → "TiDB v6.6.0より前…", matching the English "before TiDB v6.6.0" (exclusive of v6.6.0) and the section body, which already used より前.

Only heading anchors (and the one link that pointed to a renamed anchor) are changed; no prose is retranslated.

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

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 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)

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

• This PR is translated from: N/A (Japanese-only anchor/link fix; no English source change)
• Other reference link(s): part of the ja i18n-ja-release-8.5 machine-translation cleanup series

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

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: 21509350-99ca-4aef-81b3-239e2e1227ed

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 kissmydb 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