i18n(ja): translate English 'Security' to セキュリティ in Japanese prose (#23101 follow-up)

[yahonda]

What is changed, added or deleted? (Required)

Follow-up to PR #23101, which removed the Security → Security (keep in English) entry from resources/terms-en-ja.md.

This PR fixes existing Japanese documentation where 'Security' was left untranslated (due to that glossary entry) in Japanese prose contexts where セキュリティ is the natural form.

Changes across 53 files (99 changes):

• TOC navigation labels: Security → セキュリティ
• Document titles: MySQLとのSecurity互換性 → MySQLとのセキュリティ互換性, Security概要 → セキュリティ概要, etc.
• UI labels in setup steps: Securityページ, Security設定, Securityグループ, Securityクイックスタート → セキュリティ equivalents
• Feature names: Security強化モード（SEM） → セキュリティ強化モード（SEM）, Security拡張モード（SEM） → セキュリティ拡張モード（SEM）
• Protocol names in Japanese: トランスポート層Security（TLS） → トランスポート層セキュリティ（TLS）
• Link text: Securityの互換性 → セキュリティの互換性, クラスタのSecurity設定 → クラスタのセキュリティ設定
• List labels, table headers, UI tabs, etc.: All translated to セキュリティ

Preserved as-is: YAML title: front matter, {#security} anchors, English section headings (e.g. ### Security {#security}), protocol names in English context (Transport Layer Security, Mutual Transport Layer Security\'), URLs, and technical parameters (security.enable-sem, tidb_enable_enhanced_security`).

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)

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

• This PR is translated from: N/A
• Other reference link(s): Remove Security entry from EN-JA terms glossary #23101, terms: remove storage entry from EN-JA terms glossary #23100

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 breezewish 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 translates the English term "Security" to "セキュリティ" (and related terms like "セキュリティ強化モード" for "Security-Enhanced Mode") across various Japanese documentation files. The reviewer provided valuable feedback to improve the quality of the Japanese translations, including correcting missing particles (such as "が", "を", and "について"), fixing unnatural phrasing, correcting markdown syntax, and addressing a mistranslation of "Native database audit log" (which was translated as "国立データベース監査ログ").

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.