i18n(ja): unify collation terminology

[yahonda]

What is changed, added or deleted? (Required)

The database term "collation" was rendered as bare 照合 in ~30 sites across 15 files (headings, table cells, release notes), which is ambiguous with the much more common verb sense of 照合 ("match/compare," present in 100+ unrelated sentences throughout the corpus, correctly left untouched). Unified to 照合順序, matching character-set-and-collation.md's own H1 and the established database term.

Context-selective: only sites where the English source says "collation" (the noun, a sort/comparison-order setting) were changed. Sites where English says "matching"/"match" (a filter, wildcard, or ID comparison) were left as 照合する/照合される, since converting a verb use to 照合順序する would be its own new mistranslation.

Two sites needed a small restructure beyond the term swap:

• ticdc/ticdc-filter.md: one table row read "change X, then [verb]" instead of "change X and Y," matching English "modify schema charset and collate" and its sibling table row two lines below, which was already correctly structured as "change X and Y."
• ticdc/ticdc-manage-changefeed.md: restored a missing が particle before a stative passive verb.

Anchors unchanged throughout — all explicit English-derived {#...} tags.

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)?

N/A

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 icemap 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

Review skipped

Draft detected.

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: a25102d4-493d-4200-a8ca-d945999f0f43

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