i18n(ja): replace 'TiDB ダッシュボード' with 'TiDB Dashboard'

[yahonda]

What is changed, added or deleted? (Required)

Replace 'TiDB ダッシュボード' with 'TiDB Dashboard' across 162 Japanese documentation files.

Standardization:

• Replace ダッシュボード → Dashboard
• Replace キービジュアライザー → Key Visualizer
• Replace 遅いクエリ/低速クエリ → スロークエリ
• Replace クローム → Chrome
• Replace エッジ → Edge
• Replace 明細書概要表 → ステートメントサマリーテーブル
• Replace 準備されていないプラン → 非プリペアドプラン

Headings and titles:

• Fix アクセスKey Visualizerページ → Key Visualizerページにアクセスする
• Fix TiDB Dashboard TCP接続 space issue

Alert messages:

• Fix クエリP99のレイテンシーが200msを超えました → 超えた
• Fix クエリP95のレイテンシーが200msを超えました → 超えた

Grammar fixes:

• Add missing particle を before 参照してください (multiple files)
• Fix broken link in dashboard/dashboard-user.md:113
• Add missing particle を in best-practices-for-security-configuration.md:51

Footnote cleanup:

• Remove stray 1 from deploy-monitoring-services.md
• Remove stray 3 from dashboard-ops-deploy.md, sql-tuning-best-practice.md
• Remove stray 5 from post-installation-check.md, release-6.1.0.md, release-8.5.5.md
• Remove duplicate ドキュメント in release-8.5.5.md:168

Other fixes:

• Resolve conflict marker in system-variable-reference.md

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

[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

[gemini-code-assist]

Code Review

This pull request consistently updates the Japanese documentation to use "TiDB Dashboard" instead of "TiDBダッシュボード". The reviewer provided highly constructive and actionable feedback across multiple files to correct minor typos, grammatical errors, formatting issues (such as missing backticks or bold markers), and punctuation in the Japanese text. These suggestions significantly improve the natural flow, readability, and correctness of the Japanese documentation. All review comments are valid and should be kept.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.