i18n(ja): fix import related mistranslations in Japanese prose

[yahonda]

What is changed, added or deleted? (Required)

Fixed mistranslation of "import" (データインポート) as "輸入" (import of goods) across 32 Japanese documentation files.

Changes:

• 物理輸入モード → 物理インポートモード (physical import mode)
• 並行輸入 → 並行インポート (parallel import)
• 輸入 → インポート in TOC labels, UI labels, and prose
• 輸入業者 → Importer (component name)
• 輸入パフォーマンス → インポートパフォーマンス
• 完全輸入ベンチマークケース → 完全インポートベンチマークケース
• 輸入プロセス → インポートプロセス
• Data App → データアプリ (consistency fix in data-service-postman-integration.md)
• 輸入と輸出の統計 → インポートとエクスポートの統計

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

N/A (Japanese translation branch only)

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

• This PR is translated from: N/A (direct Japanese docs improvement)
• Other reference link(s): N/A

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]

[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

[gemini-code-assist]

Code Review

This pull request standardizes the Japanese technical terminology across various documentation files by replacing literal translations of "import" and "export" (such as "輸入" and "輸出") with standard IT terms ("インポート" and "エクスポート"). The review comments identify several minor grammatical errors, missing particles, and unnatural phrasing introduced by the bulk search-and-replace, offering clear and actionable suggestions to improve the overall quality and readability of the documentation.

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.