feat: handle call moderation actions [WPB-3185]

[saleniuk]

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

---

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

User needs to be informed of the actions taken towards them by the moderator/admin during the call.
In order to achieve that, these actions need to be stored, so CallModerationActionsRepository is created which stores them in memory and gives the ability to observe them. It creates a dedicated Channel for each conversation id and action type, so that the last action taken of the given type is always kept to be emitted when it starts being observed.

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

---

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.

[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

[github-actions]

Test Results

0 tests   - 4 723   0 ✅  - 4 606   0s ⏱️ - 2m 54s
0 suites  -   780   0 💤  -   117 
0 files    -   780   0 ❌ ±    0 

Results for commit ebd92fd. ± Comparison against base commit 9ccecab.

♻️ This comment has been updated with latest results.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 87.09677% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.64%. Comparing base (9ccecab) to head (ebd92fd).

Files with missing lines	Patch %	Lines
...logic/data/call/CallModerationActionsRepository.kt	90.00%	0 Missing and 2 partials ⚠️
...n/com/wire/kalium/logic/feature/call/CallsScope.kt	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4014      +/-   ##
===========================================
+ Coverage    59.63%   59.64%   +0.01%     
===========================================
  Files         2027     2030       +3     
  Lines        65541    65572      +31     
  Branches      7153     7156       +3     
===========================================
+ Hits         39085    39113      +28     
- Misses       23253    23255       +2     
- Partials      3203     3204       +1     

Files with missing lines	Coverage Δ
...ire/kalium/logic/data/call/CallModerationAction.kt	100.00% <100.00%> (ø)
...all/usecase/ObserveCallModerationActionsUseCase.kt	100.00% <100.00%> (ø)
...gic/sync/receiver/handler/CallingMessageHandler.kt	85.00% <100.00%> (+1.66%)	⬆️
...logic/data/call/CallModerationActionsRepository.kt	90.00% <90.00%> (ø)
...n/com/wire/kalium/logic/feature/call/CallsScope.kt	0.00% <0.00%> (ø)

... and 1 file 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 9ccecab...ebd92fd. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Bencher Report

Branch	feat/handle-call-moderation-actions
Testbed	ubuntu-latest

⚠️ WARNING: No Threshold found!

Without a Threshold, no Alerts will ever be generated.

• Latency (nanoseconds (ns))

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds flag.

Click to view all benchmark results

Benchmark	Latency	microseconds (µs)
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInFiles	📈 view plot ⚠️ NO THRESHOLD	891.44 µs
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInMemory	📈 view plot ⚠️ NO THRESHOLD	342,031.78 µs
com.wire.kalium.benchmarks.persistence.MessageReadBenchmark.inboxPagingDeepPageBenchmark	📈 view plot ⚠️ NO THRESHOLD	132,289.68 µs
com.wire.kalium.benchmarks.persistence.MessageReadBenchmark.inboxPagingFirstPageBenchmark	📈 view plot ⚠️ NO THRESHOLD	127,286.29 µs
com.wire.kalium.benchmarks.persistence.MessageReadBenchmark.localMarkAsReadBenchmark	📈 view plot ⚠️ NO THRESHOLD	4,224.35 µs
com.wire.kalium.benchmarks.persistence.MessageReadBenchmark.messagePagingDeepPageBenchmark	📈 view plot ⚠️ NO THRESHOLD	27,498.95 µs
com.wire.kalium.benchmarks.persistence.MessageReadBenchmark.messagePagingFirstPageBenchmark	📈 view plot ⚠️ NO THRESHOLD	11,469.66 µs
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.messageInsertionBenchmark	📈 view plot ⚠️ NO THRESHOLD	1,364,719.25 µs
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.queryMessagesBenchmark	📈 view plot ⚠️ NO THRESHOLD	21,405.19 µs

🐰 View full continuous benchmarking report in Bencher