i18n(ja): restore lost code fences (batch 6, 25 files)

[yahonda]

What is changed, added or deleted? (Required)

Continues the lost-code-fences sweep (batch 6 of the remaining files after batches 1-5: #23505, #23506, #23511, #23529, #23530). Restores dropped ``` fence markers around code/config/log examples across 25 files (tidb-cloud/*.md including 5 `terraform-use-.md` resource docs, `tidb-lightning/.md`, `tiflash/*.md`, and a few top-level files), purely structural — no visible text reworded.

Contrary to an initial concern that the 5 terraform-use-*.md files' large EN/JA count gaps might mix lost fences with genuinely untranslated new EN content, verification confirmed every block in those files was fully translated JA content that had simply lost its fence markers — no content was invented.

Verified with 3 layers: (1) total ``` count matches EN exactly, (2) block count matches EN exactly, (3) every restored block's line-by-line content has indentation identical to EN wherever the stripped content matches. This pass caught and fixed 3 additional indentation issues beyond the sub-agents' own fixes: 2 pre-existing under-indented terraform plan -generate-config-out lines (unrelated to the blocks restored in those same files) and one restored KMS JSON block that was under-indented by 4 spaces relative to EN.

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: ebe4d02d-9882-4975-914d-fa1ced11d228

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-08-17 09:58:14.298655044 +0000 UTC m=+3645280.334750101: ☑️ agreed by qiancai.