feat: foreground service for sending pending messages (WPB-26422)

[sbakhtiarov]

https://wearezeta.atlassian.net/browse/WPB-26422

https://wearezeta.atlassian.net/browse/WPB-26422

What's new in this PR?

Issues

Current solution for sending pending messages after restoring Internet connection does not work when application is not in opened by user.

Causes (Optional)

Caused by recent Android restrictions for background work:

• WorkManager work started when the application is in background is not allowed call setForeground.
• Without "setForeground" call the work cannot make network calls.

Solutions

Use foreground service which is waiting for connection and retry sending pending messages.

[pull-request-size]

Ups 🫰🟨

This PR is too big. Please try to break it up into smaller PRs.

[codecov]

Codecov Report

❌ Patch coverage is 36.31579% with 121 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.68%. Comparing base (2d2fb18) to head (d2ec791).
⚠️ Report is 12 commits behind head on develop.

⚠️ Current head d2ec791 differs from pull request most recent head 77e7efa

Please upload reports for the commit 77e7efa to get more accurate results.

Files with missing lines	Patch %	Lines
...droid/services/PendingMessagesForegroundService.kt	23.96%	92 Missing ⚠️
...tion/broadcastreceivers/DynamicReceiversManager.kt	0.00%	22 Missing ⚠️
...otlin/com/wire/android/services/ServicesManager.kt	0.00%	4 Missing ⚠️
...dcastreceivers/PendingMessagesScheduledReceiver.kt	91.66%	0 Missing and 1 partial ⚠️
...ire/android/util/lifecycle/SyncLifecycleManager.kt	91.66%	1 Missing ⚠️
...wire/android/notification/NotificationConstants.kt	0.00%	1 Missing ⚠️

❌ Your patch check has failed because the patch coverage (36.31%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4971      +/-   ##
===========================================
- Coverage    48.86%   48.68%   -0.18%     
===========================================
  Files          646      646              
  Lines        23215    23319     +104     
  Branches      3563     3568       +5     
===========================================
+ Hits         11343    11353      +10     
- Misses       10813    10917     +104     
+ Partials      1059     1049      -10     

Files with missing lines	Coverage Δ
.../kotlin/com/wire/android/GlobalObserversManager.kt	92.10% <100.00%> (+2.45%)	⬆️
...dcastreceivers/PendingMessagesScheduledReceiver.kt	91.66% <91.66%> (ø)
...ire/android/util/lifecycle/SyncLifecycleManager.kt	92.68% <91.66%> (+4.44%)	⬆️
...wire/android/notification/NotificationConstants.kt	17.39% <0.00%> (-0.80%)	⬇️
...otlin/com/wire/android/services/ServicesManager.kt	69.64% <0.00%> (-5.36%)	⬇️
...tion/broadcastreceivers/DynamicReceiversManager.kt	0.00% <0.00%> (ø)
...droid/services/PendingMessagesForegroundService.kt	23.96% <23.96%> (ø)

... and 14 files with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

@sbakhtiarov 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
56eda02b2af8c135318272348bc48af40d71815f	09ea2aeceaf73b8d0f4934722890f60bc1c3f94d

Is this intentional?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud