Unify ellipsis usage in Japanese translations

[sigma7863]

Summary

This PR unifies ellipsis usage in Japanese translations.

Changes

• Replaced ... with the single-character ellipsis …
• Normalized inconsistent ellipsis representations
• Ensured translations match the punctuation used in the original strings

Motivation

There are multiple ways to represent ellipsis (e.g., ... vs …), and some environments automatically normalize them when copying/pasting. This can lead to inconsistent display across the UI.

Using the single-character ellipsis … ensures consistent rendering and follows common Japanese typography conventions.

Scope

• Only punctuation changes (ellipsis)
• No changes to meaning or wording

[Copilot]

Pull request overview

Unifies ellipsis punctuation in the Japanese localization file to improve consistency and align with intended typography.

Changes:

• Replaced three-dot sequences (...) in Japanese translations with the single-character ellipsis (…).
• Normalized mixed ellipsis representations across multiple UI strings.
• Updated several placeholder-style translations to include ellipses where the English original includes them.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[interface.drag-and-drop.insert-links-here] has original=Insert links here (no ellipsis), but the updated translation adds an ellipsis (…). This breaks the stated goal of matching original punctuation and is inconsistent with the singular key right above (insert-link-here), which also has no ellipsis. Consider removing the ellipsis so both strings match the originals.