chore: pass short lang because svelte-i18n uses two letter language keys

[stevekaplan123]

Description

We should be passing 'en' or 'he' rather than 'english' or 'hebrew' because svelte-i18n uses two letter language keys

[gitvelocity-reviewer]

📊 Code Quality Score: 1/100

Base Score 10 × ESF 0.1 (Nano: 2 effective lines, 1 file) = 1.0

Category	Score	Factors
🔭 Scope	2/20	Single file, single line change, no new APIs or subsystems touched
🏗️ Architecture	1/20	No architectural change; minor call-site substitution within existing render method
⚙️ Implementation	2/20	Trivial one-line substitution replacing a prop reference with a utility method call
⚠️ Risk	3/20	Low risk overall; potential concern if _getShortInterfaceLang() returns unexpected format or null; affects chatbot behavior
✅ Quality	2/15	No tests added; change is too small to require them; no documentation needed
🔒 Perf / Security	0/5	No performance or security considerations addressed

_{Scored by GitVelocity · How are scores calculated?}

[YishaiGlasner]

if we submit the full language, i guess it means svelte uses it, so that seems as a breaking chage. did you check we don't assume somewhere we have the whole string?

[stevekaplan123]

if we submit the full language, i guess it means svelte uses it, so that seems as a breaking chage. did you check we don't assume somewhere we have the whole string?

That's a fair point, but I've made the relevant changes in the ai-chatbot in a separate PR.

[gitvelocity-reviewer]

📊 Code Quality Score: 1/100

10 × 0.1 (Nano ESF) = 1

Category	Score	Factors
🔭 Scope	2/20	Single file, single line change, localized to chatbot component prop
🏗️ Architecture	1/20	No architectural changes; simple prop-to-method substitution
⚙️ Implementation	3/20	Trivial substitution using correct utility method; no algorithmic complexity
⚠️ Risk	3/20	Low risk, easily reversible, localized to chatbot feature only
✅ Quality	1/15	No tests or documentation added; change is trivial and self-explanatory
🔒 Perf / Security	0/5	No performance or security considerations addressed

_{Scored by GitVelocity · How are scores calculated?}