[Enhancement] Localize launcher connector and Doctor diagnostics into Japanese

[miuuyy]

Preserving the useful localization idea from declined PR #343: show Japanese connector-verification progress and successful Doctor diagnostics in the Japanese launcher UI.

The submitted localizer has a reproduced defect: a connector named Native $& is displayed as Native {name}. It passes the name as a String.replace replacement string, which interprets replacement tokens. This also changes English and Chinese output even though those languages were intended to remain unchanged. The failure was reproduced by executing the PR function, not inferred from a screenshot.

A future implementation should localize the intended UI messages while preserving dynamic connector names and endpoints literally, retain original unknown/error messages, and leave backend/CLI diagnostics unchanged. Cover ordinary names and replacement-token/quote/backslash characters. This is a backlog enhancement, separate from the P1 stabilization work; another PR is not automatically accepted or reserved to the original implementation.

[cXSHoz]

Hi, I’ve reworked the implementation based on the issue identified in #343 and the requirements in #358.
The replacement now:

• preserves dynamic connector names and endpoints literally, including replacement-token characters such as $&, quotes, and backslashes;
• leaves English and Chinese output unchanged;
• preserves unknown, warning, and error messages as-is;
• localizes only the intended Japanese launcher success/progress messages;
• handles connector names containing U+2028/U+2029 correctly;
• only localizes Doctor entries when their status is ok.
  I also added regression coverage for these cases, including malformed input and messages with appended content.
  Verification currently passes:
• focused tests: 24/24
• launcher tests: 285 passed, 0 failed, 2 skipped
• root tests: 655 passed, 0 failed
• typecheck
• renderer build
• git diff --check
• RELOCATABLE_RUNTIME_SMOKE_OK
  The changes remain limited to the launcher localization/rendering paths and tests; backend/CLI diagnostics and IPC schemas are unchanged.
  Before opening a replacement PR, I wanted to coordinate here as requested. Does this approach match what you want for [Enhancement] Localize launcher connector and Doctor diagnostics into Japanese #358?

[miuuyy]

Completed in v5.0.6: Japanese connector-verification progress and successful Doctor checks are localized, with Chinese equivalents as well. Literal connector names/endpoints and original unknown/error messages are preserved. Thanks @cXSHoz for the contribution in #400. Closing this as resolved.