Add configurable conversation swipe actions

[sizzlesloth]

What is this?

This PR allows the left and right conversation swipe actions to be customised via the app's settings page.

Changes

• Use two separate enums for configurable swipe options vs all swipe kinds (this is because 'Unarchive' is a swipe action only available on the 'Archive' page, so not realistically configurable...)
• Implement a mapper to convert ConversationSwipeSettings (data model) to ConversationSwipeSpec (UI)
• Implement repo methods for getting the swipe (enum) pref values
• Add ConversationSwipePref prefs stuff (the application settings themselves are encapsulated under ConversationSwipeSettings
• Allow deleting conversations as a swipe option (this is primarily why I wanted to do this)
  • Note that swiping to delete a conversation will show the deletion dialogue, since there is no 'Trash' functionality and an accidental swipe would be pretty bad.
• Use a list of conversation IDs, rather than a bool to determine whether to show the deletion dialog. This allows us to share a lot of logic for deleting stuff via long press and selection vs swiping
• Refactor the set read/unread logic to do the same as the above
• Add tests to ensure custom options result in prefs being written to, null/unknown values returning safe defaults, etc.... basically in line with the existing app boolean prefs tests.

Note: Most of my experience is with Java, so I am very new to Kotlin (and Jetpack compose). I found understanding the flow for deletion and other actions quite difficult, but I have tried my best to conform to how the existing archive and set read/unread behaviours work.

Tested on an emulator and on my Pixel 8 Pro. With both main and this branch, I get performance issues on the conversations screen, so I doubt these changes are the cause.

Thanks!

mentions #351
closes #329

[RankoR]

Please fix CI and add tests for the new code.

[sizzlesloth]

@RankoR the CI/CD failures seem like an AVD graphics issue, rather than an issue with my changes? Tests have also been added. Suppose I could add an additional test for the mapper if useful?

[RankoR]

@sizzlesloth no, there were failing tests:

• debugSection_shownWhenDebugEnabled
• dumpSmsToggle_delegatesToScreenModel
• licensesClick_delegatesToScreenModel

They happen only on CI because of CI emu's screen size (320x640, 160 dpi).

Also, please cleanup commits history:

• Drop "retrigger" commit
• Rewrite history with the fixes for the tests, formatting, etc
• Rebase instead of 60b1ff8

[sizzlesloth]

Thanks @RankoR , that's good to know. The Failed to find ColorBuffer messages threw me off a bit. I've fixed the tests and rebased from main into one commit. Let me know if there's anything else I need to do!

[RankoR]

Please add tests to the changed paths. See coverage report (for both unit and instrumented tests) for the new/changed code to find what should be tested.

[RankoR]

Model should not import from mapper. One fix option is to extract that extension to a proper place.