Fix Studio CLI yargs locale strings displaying in English

[bcotrim]

Related issues

• Fixes STU-1232

Proposed Changes

• Import yargs locale JSON files directly into the bundle to bypass y18n's broken path resolution
• Use yargs.updateLocale() to apply inline locale data instead of relying on filesystem-based locale loading
• Add missing uk -> uk_UA locale mapping in mapToYargsLocale()
• Return locale data from loadTranslations() for yargs to use

Testing Instructions

Set a non-English locale in Studio UI and run studio --help:

Portuguese (Brazil):

studio --help

Verify "Comandos:", "Opções:", "Exibe ajuda" appear (not "Commands:", "Options:", "Show help")

Ukrainian:

studio --help

Verify "Команди:", "Опції:", "Показати довідку" appear

Chinese (Simplified):

studio --help

Verify Chinese characters appear for yargs strings

English:
Verify fallback to English still works correctly.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[epeicher]

Thanks for improving this @bcotrim! I have tested with multiple languages and they are all translated, with the non-translated strings falling back to English. LGTM!

Portugues (Brasil)	Ukranian	Traditional Chinese	Spanish

[epeicher]

Are these changes required?

[bcotrim]

Reverted!

[wpmobilebot]

📊 Performance Test Results

Comparing e59088d vs trunk

site-editor

Metric	trunk	e59088d	Diff	Change
load	2680.00 ms	2666.00 ms	-14.00 ms	⚪ 0.0%

site-startup

Metric	trunk	e59088d	Diff	Change
siteCreation	6083.00 ms	6076.00 ms	-7.00 ms	⚪ 0.0%
siteStartup	3941.00 ms	3945.00 ms	+4.00 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

[fredrikekelund]

bypass y18n's broken path resolution

@bcotrim, how is it broken? It's nice to fix the problem, but this seems like something that should ideally be a temporary workaround until y18n is fixed.