i18n(ja): use 時刻 for point-in-time timestamps (was 時間)

[yahonda]

What is changed, added or deleted? (Required)

Where the English source denotes a point in time (a timestamp / clock time), the Japanese used 時間 (which means a duration). This PR changes those to 時刻. Each occurrence was verified 1:1 against the English release-8.5 source; genuine durations are left as 時間.

Fixed (30 occurrences / 24 files): 作成時刻 / 更新時刻 / 開始時刻 / 終了時刻 in column/field descriptions (create_time / update_time / UPDATE_TIME), maintenance-window Start time / End time (which have a separate "Duration" field), scheduled backup start time, transaction start time, statistics-collection start/end times, etc.

Left as 時間 (durations, not touched): 実行時間, 待機時間, 処理時間, "finish duration" (grafana-pd), lease / refresh intervals (bind-info-lease, tidb_stmt_summary_refresh_interval), "arrival time intervals", "the time it takes to create a table", etc.

Note: the reference-table column descriptions in sql-plan-management / show-bindings / show-import-job / show-stats-meta / tidb-lightning-error-resolution are handled by the column-name PR, so they are not included here. sql-tuning-best-practice.md is also edited by the dropped-text PR on a nearby line (different line), so whichever merges second needs a trivial one-file rebase.

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)

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

• This PR is translated from: N/A (Japanese-only fix; no English source change)
• Other reference link(s): part of the i18n-ja-release-8.5 machine-translation cleanup series

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]

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: b92bf9c9-d264-4824-bdd8-7d1a25e93b0d

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]

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