refactor: introduce ScribeLanguage Enum to replace raw string comparisons (Part 4/6) (#426)

[prince-0408]

Description

This PR is Part 4 of 6 in modularizing GeneralKeyboardIME for #426.

It introduces a strongly-typed ScribeLanguage enum class to replace error-prone raw string comparisons (e.g., "English", "German") across keyboard services, subclasses, and helper classes.

Detailed Changes Table:

File / Component	Changes Applied	Detailed Impact
ScribeLanguage.kt [NEW]	Created ScribeLanguage enum in be.scri.models with displayName and isoCode properties, plus fromString(), fromDisplayName(), and fromIsoCode() parsing helpers.	Provides compile-time type safety for supported languages.
GeneralKeyboardIME.kt	Updated primary constructor to accept val scribeLanguage: ScribeLanguage, added overloaded string constructor, provided override val language: String get() = scribeLanguage.displayName for backwards compatibility, and replaced raw string comparisons with scribeLanguage enum checks.	Eliminates raw string checks while maintaining 100% backward compatibility.
All 8 Keyboard Subclasses	Updated EnglishKeyboardIME, FrenchKeyboardIME, GermanKeyboardIME, ItalianKeyboardIME, PortugueseKeyboardIME, RussianKeyboardIME, SpanishKeyboardIME, and SwedishKeyboardIME constructors to pass ScribeLanguage enum instances (e.g. ScribeLanguage.ENGLISH).	Strongly types language instantiation across all IME subclasses.
LanguageMappingConstants.kt	Updated getLanguageAlias() to support ScribeLanguage enum directly.	Streamlines language alias lookup logic.

---

Key Benefits:

• Compile-time Safety: Replaces magic string literals with strongly-typed ScribeLanguage enum values.
• Maintainability: Centralizes language metadata (displayName, isoCode) in a single source of truth.
• Zero Behavioral / API Breakage: Retains string accessor language: String so existing callers continue working seamlessly.

---

Related Issue

Refactors part of #426

[andrewtavis]

quick note, @prince-0408: Could we ask that you not have resolve #ISSUE_NUMBER is your PR messages? You're doing it correctly in the Related Issue section of the comment, but your first sentence - before I edited it - was "This PR is Part 4 of 6 in modularizing GeneralKeyboardIME to resolve #426." That will close the issue if we were to merge :)

[prince-0408]

quick note, @prince-0408: Could we ask that you not have resolve #ISSUE_NUMBER is your PR messages? You're doing it correctly in the Related Issue section of the comment, but your first sentence - before I edited it - was "This PR is Part 4 of 6 in modularizing GeneralKeyboardIME to resolve #426." That will close the issue if we were to merge :)

Thanks so much for heads-up and for editing that, @andrewtavis!

Got it! I will make sure to use for #426 or refactoring part of #426 instead of resolve #426 in all future PR descriptions so the main issue stays open.

[andrewtavis]

Would you be able to fix the merge conflicts here, @prince-0408?

[andrewtavis]

I'll get to the review soon after :)

[prince-0408]

Would you be able to fix the merge conflicts here, @prince-0408?

Hi @andrewtavis

I have resolved all merge conflicts with upstream/main on PR #672, formatted the code.

Ready for your review whenever you have a moment. Thanks! 😊

[andrewtavis]

praise: All's working well here, @prince-0408! Thanks for this and the many other PRs recently 😊