i18n(ja): restore lost code fences (batch 4, 35 files)

[yahonda]

What is changed, added or deleted? (Required)

Continues the lost-code-fences sweep (batch 4 of the remaining files after batches 1-3: #23505, #23506, #23511). A machine-translation pipeline used previously sometimes dropped the ``` fence markers around code/config/log examples when translating EN to JA, leaving the example content bare (sometimes with a leftover 4-space "indented code block" artifact). This is a purely structural fix — no visible text was reworded.

35 files, restored via 3 parallel sub-batches. Every file verified with 3 layers of checking: (1) total ``` count now matches EN exactly, (2) block count matches EN exactly, (3) every restored block's line-by-line content, after stripping any leading blockquote > markers, has indentation identical to EN wherever the stripped content matches EN's line.

Also fixed 2 small adjacent defects found while restoring fences in the same lines:

• storage-engine/rocksdb-overview.md: a stray tilde standing in for a dropped particle (`rocksdb/max-background-jobs`～3または4を調整してください → `rocksdb/max-background-jobs`を3または4に調整してください)
• sync-diff-inspector/sync-diff-inspector-overview.md: a stray <!----> MDX marker artifact left over from the missing fence, removed to match EN's plain blank line

Re-scanned the corpus fresh before starting this batch (per lessons from prior batches that the candidate list can go stale) — confirmed no new regressions from the daily translation-sync bot; the previously-flagged inline-triple-backtick-escape false positives (dm/deploy-a-dm-cluster-using-tiup*.md, dm/handle-failed-ddl-statements.md, production-deployment-using-tiup.md) are still correctly excluded.

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)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)

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

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

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: e9531b67-37f2-4fca-89a0-6543ef0f817a

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]

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

[CLAassistant]

All committers have signed the CLA.