fix: start foreground CallService crashes [WPB-24829][WPB-24840]

[saleniuk]

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

---

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?

• Empty conversation name on call notifications - now it’s secured and if empty then it always uses some default text.
• Added missing title and “immediate” behavior for placeholder notification.
• Moved starting foreground to be the very first action in onStartCommand to avoid any delays.
• Added creating a notification channel before starting foreground to ensure the channel is already created when needed.
• Added microphone permission check before starting foreground and a fallback when not - in that case it starts foreground with type not requiring permission (it needs to be started anyway to avoid other crashes) and then closing the call and stopping service afterwards as the call won’t work otherwise.
• Created custom StartForegroundException with some more info to be able to better investigate crashes in the future.
• Updated the code for ending call when user is no longer in a conversation to do it for all active accounts instead of only the first one on the list (it was a bug).
• Fixed the logic of clearing notifications and stopping the service if there are no active users - we have two ways of syncing: pushes or persistent socket and we handle both user lists separately and the logic was checking if the given sub-list is empty to clear it for all users so in case the “push” list is empty and user only uses persistent socket, then app could close the service and clear all notifications for that user if it noticed that the other list is empty. Now, it checks if the user list is empty before splitting these two lists, so does it taking all users into account at once.
• Added waiting for the completion of the initial clean-up of stale open calls (to be changed to closed) when the app starts, before starting observing calls in order to start the CallService, to avoid starting the service by mistake for the calls that are already stale.

Dependencies (Optional)

Needs releases with:

• fix: set and observe stale open calls cleanup [WPB-24829] kalium#4134

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

How to Test

Start a call, kill the app, open again. Disable microphone permissions and try to start or join a call. Starting the call should not crash.

---

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.

[github-actions]

@saleniuk 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
f69a608d5126385b2a1284845657c0bbf11f9c65	53b0fcb4f74d61bfb51635f074236714cba44ec9

Is this intentional?

[github-actions]

@saleniuk 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
f69a608d5126385b2a1284845657c0bbf11f9c65	00bdcd1bc44c36e9f7fe8a19058e380029f17085

Is this intentional?

[github-actions]

@saleniuk 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
f69a608d5126385b2a1284845657c0bbf11f9c65	00bdcd1bc44c36e9f7fe8a19058e380029f17085

Is this intentional?

[github-actions]

@saleniuk 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
f69a608d5126385b2a1284845657c0bbf11f9c65	00bdcd1bc44c36e9f7fe8a19058e380029f17085

Is this intentional?

[codecov]

Codecov Report

❌ Patch coverage is 54.02299% with 40 lines in your changes missing coverage. Please review.
✅ Project coverage is 51.76%. Comparing base (951a019) to head (d1d65ea).

Files with missing lines	Patch %	Lines
...in/kotlin/com/wire/android/services/CallService.kt	0.00%	23 Missing ⚠️
...re/android/notification/CallNotificationManager.kt	40.90%	11 Missing and 2 partials ⚠️
...in/com/wire/android/services/CallServiceManager.kt	82.35%	1 Missing and 2 partials ⚠️
...ndroid/notification/NotificationChannelsManager.kt	0.00%	1 Missing ⚠️

❌ Your patch check has failed because the patch coverage (54.02%) 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    #4820      +/-   ##
===========================================
+ Coverage    51.29%   51.76%   +0.46%     
===========================================
  Files          611      611              
  Lines        21201    21256      +55     
  Branches      3407     3410       +3     
===========================================
+ Hits         10875    11003     +128     
+ Misses        9310     9234      -76     
- Partials      1016     1019       +3     

Files with missing lines	Coverage Δ
.../kotlin/com/wire/android/GlobalObserversManager.kt	89.65% <100.00%> (+0.97%)	⬆️
...re/android/notification/WireNotificationManager.kt	75.78% <100.00%> (+2.50%)	⬆️
...wire/android/notification/NotificationConstants.kt	18.18% <ø> (+9.09%)	⬆️
...ndroid/notification/NotificationChannelsManager.kt	0.99% <0.00%> (ø)
...in/com/wire/android/services/CallServiceManager.kt	91.66% <82.35%> (-2.98%)	⬇️
...re/android/notification/CallNotificationManager.kt	64.61% <40.90%> (+26.02%)	⬆️
...in/kotlin/com/wire/android/services/CallService.kt	9.85% <0.00%> (-2.43%)	⬇️

... and 4 files with indirect coverage changes

---

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 951a019...d1d65ea. 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]

@saleniuk 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
cc41a919dacdfbc4c82ceff0493a1e09f0d7a46a	00bdcd1bc44c36e9f7fe8a19058e380029f17085

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