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

[yahonda]

What is changed, added or deleted? (Required)

Continues the lost-code-fences sweep (batch 5 of the remaining files after batches 1-4: #23505, #23506, #23511, #23529). Restores dropped ``` fence markers around code/config/log examples across 25 files (mostly ticdc/*.md and `tidb-cloud/*.md`), purely structural — no visible text reworded.

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, after stripping leading blockquote > markers, has indentation identical to EN wherever the stripped content matches.

data-service-manage-endpoint.md needed no fix: its apparent EN/JA count gap is fully explained by 6 EN lines using inline triple-backtick delimiters around short path examples (e.g. ```/var/{var}```), which JA correctly renders with single backticks for the same content — not a lost fence.

Also fixed 3 pre-existing indentation mismatches found during verification in ticdc-sink-to-kafka.md (already-fenced --sink-uri examples using a 4-space indent instead of EN's 2-space; unrelated to the lost-fence blocks restored on the same file, caught by the same verification pass).

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

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

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: 4fb9a87b-7607-4b6b-93aa-1a38b5bb44cb

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

[CLAassistant]

All committers have signed the CLA.