Add community Russian language pack (v1.3.6 for Orca 1.4.224)

[taranttoola-create]

What this adds

A community Russian (ru) language pack for Orca: taranttoola-create.russian.

• Coverage: 15,706 translated strings (17,649 catalog entries with nesting) synced against Orca 1.4.224.
• Source: https://github.com/taranttoola-create/orca-russian (tag v1.3.6). Mirror: https://gitverse.ru/buheirf/orca-russian
• No executable code. The plugin is one JSON catalog declared through contributes.languagePacks; capabilities is empty and no worker/panel files exist.
• Protected paths respected: the 180 auto.components.settings.Plugin* trust-dialog paths are not in the catalog (except the 34 allow-listed chrome paths), and no value exceeds 8192 characters.
• Verification: the catalog passes Orca's own plugin-language-pack-artifact validator (extracted from app.asar 1.4.224 — byte-identical to the 1.4.222 rules), with 0 placeholder drift against en.json.

What changed in v1.3.6

• +560 new translations, −50 obsolete keys, 21 changed English texts refreshed since 1.4.222.
• Managed Orca servers on SSH hosts (134 strings), native chat: rewind, attachments, in-chat search, queued messages (200), workspace links to GitHub/GitLab/Linear/Jira/Bitbucket/Azure DevOps/Gitea (65), chat appearance (32), nested-worktree deletion (12), Markdown callouts (5), project views (8).

Checks run

• validate-catalog.mjs --with-en en-1.4.224.json: catalog valid, 17,649 entries (< 20,000), 1,408 KB (< 5 MB), no placeholder drift, 0 translatable strings missing.
• i18next smoke test: new keys resolve to Russian through t() with interpolation and both plural forms.
• Clean clone of tag v1.3.6 re-validated; catalog byte-identical to the released file.
• orca-marketplace.json in this PR parses under pluginMarketplaceSchema from Orca 1.4.224 and the id is not reserved.

Notes

• 139 keybinding.* entries are pre-staged translations awaiting i18n: shortcut action titles and group names are not localizable (hardcoded in the keybinding registry) orca#25048; they are inert while Orca hardcodes shortcut titles.
• Russian needs 4 plural forms; Orca supports _one/_other, so 2–4 renders the _other form (tracked in fix(i18n): resolve plugin-pack plurals with the declared locale orca#12505).

[taranttoola-create]

Rebased the entry onto v1.3.0 and bumped the title to match — the ref in the diff was already v1.3.0, the title had gone stale at v1.2.0.

Context for review, since there are several Russian packs in flight here (#1, #3, #6):

• Pack: taranttoola-create.russian, catalog 14,551 entries against the 14,733-key en.json of 1.4.212. The 182-key gap is structural, not unfinished work — 180 protected auto.components.settings.plugin* paths plus two oversize values (documented in tooling: scaffold and re-sync helper for plugin language packs orca#20508).
• Verified against the 1.4.196+ install pipeline: manifest schema, artifact limits (5 MB language pack, 2000 entries, no symlinks), catalog validation via plugin-language-pack-artifact.js, and the reserved-identity rule.
• Install has been exercised end-to-end on 1.4.212, not just validated offline.

Two process questions, whichever is easier to answer:

1. Is the intent for community entries to stay outside this index and be added by users as a marketplace source, or should they land here? #9207 points authors at the marketplace, but this repo hasn't merged any of the 10 open submissions yet, so it's hard to tell what you want.
2. If entries shouldn't carry official, is languages alone the right category, and do you want a separate marker so users can tell curated entries from community ones?

Happy to reshape the entry to whatever fits — and to close this in favor of #6 or #3 if you'd rather consolidate on a single Russian pack.