i18n(ja): restore more literal identifiers mistranslated into Japanese (batch 2)

[yahonda]

What is changed, added or deleted? (Required)

Continuation of the literal-identifier-mistranslation sweep (#23617/#23618/#23619). 7 more sites across 7 files, all verified against the English source:

• releases/release-6.2.0.md: replication-mode.dr-auto-sync.wait-async-timeout / wait-sync-timeout config keys restored (were レプリケーションモード.dr-auto-sync...)
• develop/dev-guide-third-party-support.md: Hibernate version 6.1.0.Final restored (was 6.1.0.最終版)
• releases/release-7.1.0.md, releases/release-6.5.2.md: literal cgroup error message text restored — memory.stat had been partially translated to メモリ.stat inside the quoted error string
• develop/dev-guide-playground-gitpod.md: example.gitpod.yml link text restored (was 例.gitpod.yml)
• tiup/tiup-component-cluster-check.md: topology.yml link text restored (was トポロジー.yml, inconsistent with 3 other literal mentions of the same filename in the same file)
• table-filter.md: 5 example table-filter rows restored to their literal EN table names — employees.dept_emp and employees.departments had both collapsed to identical JA text 従業員.部門, losing the distinction between the two example rows entirely

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): continuation of i18n(ja): restore literal dotted config/API identifiers mistranslated into Japanese #23617/i18n(ja): keep literal TiDB error message text in English #23618/i18n(ja): keep the literal information_schema identifier in table-page summaries #23619

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

[coderabbitai]

Warning

Review limit reached

Next included review available in 21 minutes.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 281abd12-cc5a-466b-8740-590602ea812d

📥 Commits

Reviewing files that changed from the base of the PR and between d41688a and e0d02a8.

📒 Files selected for processing (7)

• develop/dev-guide-playground-gitpod.md
• develop/dev-guide-third-party-support.md
• releases/release-6.2.0.md
• releases/release-6.5.2.md
• releases/release-7.1.0.md
• table-filter.md
• tiup/tiup-component-cluster-check.md

---

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