feat: add more message status icons

[trOnk12]

---

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

• Add support for read message status and delivered.

Needs releases with:

(wireapp/kalium#1943)

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

---

PR Post Submission Checklist for internal contributors (Optional)

• Wire's Github Workflow has automatically linked the PR to a JIRA issue

---

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.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

@trOnk12 looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop	This PR
67514c7ec1394fbb477c9c3fb92600838f2642a5	ad652616b8ac3394a640a38822b47d5c900d2c38

Is this intentional?

[github-actions]

Test Results

509 tests  ±0   508 ✔️ ±0   5m 37s ⏱️ -27s
  77 suites ±0       1 💤 ±0 
  77 files   ±0       0 ❌ ±0 

Results for commit ac950f9. ± Comparison against base commit b741209.

♻️ This comment has been updated with latest results.

[AndroidBob]

Build 840 failed.

[AndroidBob]

Build 863 failed.

[AndroidBob]

Build 917 failed.

[codecov]

Codecov Report

Merging #2045 (ac950f9) into develop (b741209) will decrease coverage by 0.02%.
The diff coverage is 30.76%.

@@              Coverage Diff              @@
##             develop    #2045      +/-   ##
=============================================
- Coverage      39.10%   39.08%   -0.02%     
  Complexity       920      920              
=============================================
  Files            305      305              
  Lines          11179    11182       +3     
  Branches        1490     1494       +4     
=============================================
- Hits            4372     4371       -1     
- Misses          6386     6388       +2     
- Partials         421      423       +2     

Files Changed	Coverage Δ
...in/kotlin/com/wire/android/mapper/MessageMapper.kt	60.78% <22.22%> (-1.85%)	⬇️
...e/android/ui/home/conversations/model/UIMessage.kt	43.98% <50.00%> (-0.35%)	⬇️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b741209...ac950f9. Read the comment docs.

[github-actions]

APKs built during tests are available here. Scroll down to Artifacts!

[AndroidBob]

Build 949 succeeded.

The build produced the following APK's:

• com.wire.android-v4.4.0(7252082)(7252082)-staging-compat.apk

[github-actions]

APKs built during tests are available here. Scroll down to Artifacts!

[github-actions]

APKs built during tests are available here. Scroll down to Artifacts!

[AndroidBob]

Build 986 succeeded.

The build produced the following APK's:

• com.wire.android-v4.4.0(7261381)(7261381)-staging-compat.apk