Fix Raft ready/apply jargon mistranslated as generic Japanese words

[yahonda]

What is changed, added, or deleted? (Required)

Fixes the Raft-internal jargon terms ready (the etcd/raft Ready struct/batch of entries-messages-snapshot to process) and apply (applying a committed log entry/proposal to the state machine) that were mistranslated using their generic-dictionary sense (準備完了 "preparation complete" and 適用 "apply/use a setting") instead of the specific Raft jargon sense. This is the same defect class found and fixed in PR #23781 (grafana-tikv-dashboard.md); this PR extends the same fix to the rest of the corpus. Verified via docs-cn, which keeps both terms as literal, untranslated English throughout the equivalent sections.

Files changed:

• alert-rules.md: 3 alert descriptions (apply log duration, apply thread, process ready duration).
• deploy-monitoring-services.md: 1 monitoring bullet (Raft processes the ready state).
• dashboard/dashboard-monitoring.md and grafana-performance-overview-dashboard.md: restored literal English Grafana/TiDB Dashboard panel headings and metric labels across the whole file (same panel-name defect class as PR i18n(ja): restore literal English Grafana panel names in dashboard docs #23763/i18n(ja): restore literal English Grafana panel names in TiKV dashboard doc #23781, not yet applied to these two files), plus fixed the apply-loop/apply-log body descriptions.
• performance-tuning-methods.md: fixed a scrambled Apply Log Duration table row (kept consistent with the file's own already-established 適用ログ期間 heading wording, checked against docs-cn); left the file's other 適用 occurrences (apply a formula/algorithm) untouched since those are generic usage.
• tidb-cloud/built-in-monitoring.md: 3 metric-table description cells (apply duration, apply log duration).
• tikv-configuration-file.md and dynamic-config.md: config-item descriptions for max-apply-unpersisted-log-limit, apply-pool-size, apply-yield-write-size, min-pending-apply-region-count, and enable-async-apply-prewrite.
• tune-tikv-thread-performance.md: 1 thread-pool description (Apply thread), matching the file's own existing capitalized usage.
• troubleshoot-stale-read.md: 6 sites describing safe-ts/resolved-ts and apply index semantics.
• latency-breakdown.md: 2 sites (async-write Apply phase, apply duration from RocksDB perf context).
• releases/release-7.1.6.md, release-7.5.4.md, release-7.5.5.md, release-7.5.6.md, release-7.5.7.md: the recurring "waiting for the log to be applied" TiKV-restart release note.
• releases/release-8.2.0.md: 3 sites, including 早期応募 ("early job application"), a homonym mistranslation of the "early apply" feature name, confirmed against docs-cn's 提前 apply.
• tidb-cloud/v8.5-performance-highlights.md: 1 site (leader applying Raft logs early).

Left untouched after per-site verification against the real EN source: release-7.5.4.md's tidb_redact_log line, release-8.2.0.md's privilege-control line, release-8.5.8.md's flow-control/BR-log-restore/TiCDC-DML-apply lines (a different, TiCDC/BR redo-log-apply concept, not TiKV's raftstore Apply), and several generic apply-a-formula/algorithm/constraint sites in tikv-configuration-file.md and performance-tuning-methods.md — all of these use "apply"/"ready" in the ordinary generic-English sense, not the Raft-specific jargon sense.

Which TiDB version(s) do your changes apply to? (Required)

• v8.5 (TiDB 8.5 versions)

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

• Related code change PR links (if applicable):
• This PR is translated from:
• Other reference link(s): follow-up to i18n(ja): restore literal English Grafana panel names in TiKV dashboard doc #23781

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

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

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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

[yahonda]

Closing per a policy reversal: decided to revert the Raft ready/apply literal-English decision entirely (see #23781's latest commit) and keep the original Japanese translations (準備完了/適用). This PR's whole purpose was that literal-English conversion, so it's now moot.