i18n(ja): restore genuine 2-word TiDB Cloud UI labels to English

[yahonda]

Summary

These 228 candidate labels were skipped by the mechanical 2-word batch (#23535) because they couldn't be confirmed via a plain dbaas-ui grep — mostly third-party console fields (AWS, Azure, Alibaba Cloud, GCP, Kafka, Datadog, New Relic, n8n, Airbyte, PagerDuty, Slack) that dbaas-ui doesn't cover, plus a handful of TiDB-native labels the grep missed.

Each candidate was individually triaged against EN (release-8.5) and, for TiDB-native items, dbaas-ui with a strict STRONG/WEAK/COMMENT_ONLY/NO_HIT classifier, distinguishing genuine clickable UI elements from prose/marketing/category-header bullets that merely share the same words (the "No cost"/"High availability" false-positive pattern from earlier batches).

265 occurrences fixed across 47 files. ~70 further candidates were deliberately left in Japanese as category-header/concept-heading prose, not clickable UI (same precedent as architecture-concepts.md).

Along the way this also fixed several pre-existing defects surfaced by the same EN comparison:

• Mismatched AWS IAM button-label pairs (Attach Policies vs Attach Policy previously translated as the same word)
• Particle- and bracket-trapped-in-bold spans (including the [仮想**ネットワーク]** defect flagged earlier this session)
• Word-order/position-pairing mis-mappings (Source/Target engine, Signing method/Account key, Export Path)
• A mistranslation (一般公開→Public accessible)
• An orphaned bracket left over from an incomplete straddling-bracket fix

Import dashboard (monitor-new-relic-integration.md) was explicitly skipped — already handled by #23540.

⚠️ Known conflicts with other open PRs

This PR's base is the same tip as #23535, and the two independently touch many of the same files (~40 overlapping lines). I already worked out and verified the correct merged resolution for all 40 conflicting hunks (combining whichever side had already progressed a given label to English, plus a few extra fixes found while reconciling: a dropped particle in VPC Peeringを, an incorrect Signing method/Account key field-value swap, and a garbled Availability zone label). That resolution is not included in this PR's diff (to keep this PR's diff scoped to only its own new content), but is ready to hand to whoever merges these two PRs — ping me and I'll apply it directly.

While working out that resolution, I also discovered (but have not fixed, as it's out of this PR's scope) that #23535 independently conflicts with #23519 (3/4-word batch, ~142 conflict markers) and with #23516 (Note-label normalization, ~3 conflict markers). Both are pre-existing conflicts between those two already-open PRs, unrelated to this PR's changes — flagging for whoever sequences the merge order.

Test plan

• 0 bracket/**-parity/paren-balance issues in the diff (automated check)
• Every FIX verified 1:1 against EN (release-8.5), spot-checked a random sample of 20+ across all 6 triage batches
• 0 conflicts against 13 of the 15 other open sibling branches (the 2 exceptions — i18n(ja): restore 4-word and 3-word TiDB Cloud UI labels to English #23519 and i18n(ja): restore English admonition labels #23516 — conflict with i18n(ja): restore 2-word TiDB Cloud UI labels to English #23535 itself, not with this PR; see note above)

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

🗂️ Base branches to auto review (3)

• ^master$
• ^release-8.5$
• ^ja/update-pr-template$

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b9e0d371-95ae-4d3c-925f-814b0d236929

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]

[LGTM Timeline notifier]

Timeline:

• 2026-08-19 02:38:34.47531203 +0000 UTC m=+37349.646406133: ☑️ agreed by qiancai.

[qiancai]

@yahonda, before I merge this pull request, would you please confirm whether the changes in this pull request are ready for merge? If so, please remove "unconfirmed patch" from the pull request title.

[yahonda]

Thanks for the review. I have updated the subject. Let me resolve the conflict then.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[yahonda]

Closed since #23545 has been merged.