chore: add support for jetpack paging on persistence (AR-1882)

[vitorhugods]

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

On Android, dealing with LazyColumn + manual implementation of Paging with reactive data is a bit painful.

Solutions

Add support for Jetpack Paging on Android, using SQLDelight's extensions for that.

Issues with SQLDelight implementation

There are a few issues related to the current implementation of PagingSource on SQLDelight. Especially for us that are a few versions behind and can't upgrade right now:

• Shrinking a query observed by OffsetQueryPagingSource in Android paging3 causes an exception cashapp/sqldelight#2591
• IndexOutOfBoundsException In OffsetQueryPagingSource cashapp/sqldelight#2434

Because of this, I've altered the implementation in a couple of lines to suit our needs.

Platform-specific extension

Adding a platform-specific extension was a first (I believe ?) to this project.
The chosen approach was to create an expect class MessageExtensions that is added to the current MessageDAO.
This way, each platform can create its own extensions on their actual implementation of the MessageExtensions.
The alternative would be flipping this completely upside-down, like UserSessionScope does:
A MessageDAOCommon and actual implementations of MessageDAO that extend the common implementation. However, empty extension classes seem easier to maintain than creating empty actual implementations of the main behaviour.

Small refactoring on MessageMapper

As the mapper is needed for both the MessageDAO and the MessageExtensions, I've moved it to its own file, and moved some of the mapping functions from the DAO to the Mapper, as it probably should've been done before anyway. This way these functions can be used by both classes.

Testing

Test Coverage

• I have added automated test to this contribution

---

PR Post Merge Checklist for internal contributors

• If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[github-actions]

Unit Test Results

   195 files   -   19     195 suites   - 19   1m 35s ⏱️ + 1m 17s
1 051 tests +    5  1 038 ✔️  -     2  13 💤 +7  0 ❌ ±0 
1 837 runs  +791  1 824 ✔️ +784  13 💤 +7  0 ❌ ±0 

Results for commit 1a722e2. ± Comparison against base commit 75cbb7c.

♻️ This comment has been updated with latest results.

[codecov-commenter]

Codecov Report

Merging #886 (1a722e2) into develop (75cbb7c) will decrease coverage by 0.01%.
The diff coverage is 30.90%.

@@              Coverage Diff              @@
##             develop     #886      +/-   ##
=============================================
- Coverage      60.36%   60.35%   -0.02%     
- Complexity       673      679       +6     
=============================================
  Files            455      456       +1     
  Lines          12114    12127      +13     
  Branches        1223     1225       +2     
=============================================
+ Hits            7313     7319       +6     
- Misses          4279     4286       +7     
  Partials         522      522              

[Garzas]

LGTM 🎸