Migrated language settings screen from XML to Jetpack compose

[Saifuddin53]

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

The pull request moves the language settings page to Jetpack Compose and has refactored the settings composable to use the reusable components that were created in this PR

Screenshots

Settings:

Before	After

Language Settings:

Before	After

• #ISSUE_NUMBER
  Migrate the Language settings page to Jetpack Compose  #253

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. 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 :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Android rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The linting and formatting workflows within the PR checks do not indicate new errors in the files changed

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

[github-actions]

First PR Commit Check

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution
  - The contributor's name and icon in remote commits should be the same as what appears in the PR
  - If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-Android repo

[Saifuddin53]

@andrewtavis @angrezichatterbox Ready for review

[andrewtavis]

Thanks for the quick work here, @Saifuddin53! I'll get to my review this weekend 😊 Great to have you on the project :)

[andrewtavis]

Had a moment to check the UI and it's all looking great 😊 Thanks @Saifuddin53 and @angrezichatterbox for working towards such a professional and technologically sound application :) @angrezichatterbox, do you want to do a quick check of the code and then we can bring this in?

[angrezichatterbox]

@Saifuddin53, your work on refactoring the compose codebase into reusable and maintainable components is truly impressive. The page you’ve created is also amazing. I hope we’ll see you around solving more issues in the future.

There are a few linting issues that could be resolved by running ./gradlew formatKotlin.

[angrezichatterbox]

This is currently not being used right and could be removed or the codebase could be modified to use them.

[Saifuddin53]

The enum class is no more of use and the other two data classes can be used in the future when we migrate the About page to compose

[Saifuddin53]

Thank you so much, @andrewtavis and @angrezichatterbox, for your encouraging words and support! 😊. Looking forward to collaborating on more exciting issues in the future.

@angrezichatterbox, I’ve resolved the linting issues as you suggested and have removed the unused code.

[angrezichatterbox]

Everything looks Great now :)

[andrewtavis]

Thank you both for the amazing collaboration here for a great result! 😊 Looking forward to the next issue, @Saifuddin53 🚀