Refresh shared UI i18n handling

[52sanmao]

Background

This is the companion shared UI i18n change for vrtmrz/obsidian-livesync#878.

The parent PR uses shared setup UI components with i18n message keys. Those components also need to remain safe for existing callers that pass literal or dynamic strings.

Purpose

• Let shared UI controls translate known message keys automatically.
• Avoid false missing-translation noise when a prop is plain text rather than an i18n key.
• Complete and refresh the shared translation resources used by the parent runtime-language update.
• Keep shared setup components usable from both translated and non-translated call sites.

Changed Files

• src/UI/components/**

  • Routes label-like props through translateIfAvailable().
  • This keeps component callers simple: they can pass message keys when available, while plain strings still render as-is.

• src/common/i18n.ts

  • Provides the safe translation helper used by shared components.
  • The helper exists so components do not need to decide whether a string is always a key.

• src/common/messagesYAML/**

  • Adds or updates shared UI translation entries used by the setup/settings i18n flow.

• src/common/messages/** and src/common/messagesJson/**

  • Refreshes generated message output from the updated translation source files.
  • Keeps the generated resources aligned with the supported runtime languages.

Verification

Verified through the parent obsidian-livesync build using this submodule commit:

• npm run tsc-check
• npm run svelte-check
• npm run build
• git diff --check
• git -C src/lib diff --check

Compatibility / Notes

• Plain text callers should keep working because translation is conditional.
• This PR is required by Improve i18n coverage and runtime language updates obsidian-livesync#878

[vrtmrz]

Thank you for your PR!
I have merged the other PRs one by one, but I am afraid this PR has resulted in quite a few differences.
I would have merged it myself if it were any other file, but unfortunately, I am not very good at Chinese, so may I ask you to compare it with the latest main branch and resolve it using the correct version, please?

[vrtmrz]

@52sanmao Sorry for not getting in touch.

As I had made a significant diff, I have made some adjustments to align your PR with the Main branch.

I am not entirely sure if I have managed to preserve the content of your PR, so would you please check it for me? If it looks OK, I will l merge it!

[vrtmrz]

I am sorry to share that, while preparing v1.0.0, we changed the project boundary: application translations and dialogues now live in the main Self-hosted LiveSync repository, while Commonlib keeps its canonical English service messages and translation-injection boundary. This should make future contributions easier to locate, understand, and merge.

I am sorry to ask for additional work after you prepared this PR. Would you be willing to open a new PR against Self-hosted LiveSync using the current structure? Thank you again for your contribution and patience.