Refactor/keyboard UI manager

[bhanu-dev82]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have tested my code with the ./gradlew lintKotlin detekt test command as directed in the testing section of the contributing guide

---

Description

This pull request refactors GeneralKeyboardIME to improve separation of concerns by extracting UI-related logic into a dedicated KeyboardUIManager.

Summary of changes

• Extracted UI handling logic from GeneralKeyboardIME.kt into a new KeyboardUIManager.kt
• Simplified GeneralKeyboardIME so it focuses primarily on InputMethodService lifecycle and coordination
• Updated existing tests by refactoring GeneralKeyboardIMETest.kt to reflect the new architecture
• Added new test coverage in KeyboardUIManagerTest.kt to validate UI state handling independently

Related issue

Closes #540

[github-actions]

Thank you for the pull request! 💙

The Scribe-Android team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest that you use the Element client as well as Element X for a mobile app, and definitely join the General and Android rooms once you're in. Also consider attending our bi-weekly Saturday dev syncs. It'd be great to meet you 😊

Note

Scribe uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• Tests for changes have been written and the unit test, linting and formatting workflows within the PR checks do not indicate new errors in the files changed

  • Tests may need to be reran as they're at times not deterministic

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Thanks for the issue and the PR, @bhanu-dev82! We'll try to finalize the review in the coming days :)

[angrezichatterbox]

Amazing work @bhanu-dev82
Thanks for adding the tests along with it.

[andrewtavis]

Would one of you be able to fix the failing tests, @bhanu-dev82 or @angrezichatterbox? :)

[angrezichatterbox]

I would be able to look into it later today evening.

[angrezichatterbox]

@andrewtavis It is ready for review :)

[andrewtavis]

praise: Hey @bhanu-dev82 and @angrezichatterbox! All's generally working well, and this is really improving the structure of the code!
note [blocking]: I noticed one thing that should be fixed before merge. The color of the shift key isn't changing anymore, so you don't know if you'll be typing a capital letter or are in caps lock anymore. Could we take a look as to why this is happening?

[angrezichatterbox]

praise: Hey @bhanu-dev82 and @angrezichatterbox! All's generally working well, and this is really improving the structure of the code! note [blocking]: I noticed one thing that should be fixed before merge. The color of the shift key isn't changing anymore, so you don't know if you'll be typing a capital letter or are in caps lock anymore. Could we take a look as to why this is happening?

I would look into it now

[andrewtavis]

Looks like we'll need to run update_i18n_keys.sh to fix the merge conflicts here as well, @angrezichatterbox :)

[andrewtavis]

Just ran update_i18n_keys.sh on main, so we shouldn't have conflicts there once the branch has the latest commit :)

[angrezichatterbox]

I am not sure if what I did is right. Could you have a look @andrewtavis for the submodule

[andrewtavis]

praise: All's working perfectly now, @bhanu-dev82 and @angrezichatterbox! Thank you both for this whole process! A very important issue, a great execution and also finishing touches to bring all of this in 😊