ci: remove ZH dispatch from JA translation cron

[qiancai]

What is changed, added or deleted? (Required)

Remove the dispatch-translation-zh job from translation-cron.yml so the JA translation cron no longer dispatches the ZH translation workflow.

Also rename the workflow to Translation Cron JA and clarify the JA-related schedule and matrix comments.

This avoids duplicate ZH translation runs because translation-zh.yaml already has its own scheduled trigger.

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

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 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)

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

• This PR is translated from: N/A
• Other reference link(s): translation-zh.yaml already schedules ZH translation directly.

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

Validation

• git diff --check -- .github/workflows/translation-cron.yml
• ruby -e 'require "yaml"; YAML.load_file(".github/workflows/translation-cron.yml"); puts "YAML ok"'

[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

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

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

[qiancai]

Closing in favor of a replacement PR from a branch without the codex prefix.