fix: MLS groups are not usable if I have a proteus client registered to my account but have MLS on current client [WPB-15192] 🍒

[github-actions]

WPB-15192 [Android] MLS groups are not usable if I have a proteus client registered to my account but have MLS on current client

This PR was automatically cherry-picked based on the following PR:

• fix: MLS groups are not usable if I have a proteus client registered to my account but have MLS on current client [WPB-15192] #3197

Original PR description:

---

---

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

the current client can be MLS capable but it did not announce it yet to the backend (migration is not forced yet)

Solutions

instead of looking at the user in general to know if interactions are allowed only look at the current client
this will result to the current client ignoring any Proteus self clients when sending but this is an acceptable case

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

Needs releases with:

• GitHub link to other pull request

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)

Attachments like images, videos, etc. (drag and drop in the text box)

---

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

3 384 tests  +5   3 276 ✅ +4   5m 27s ⏱️ -7s
  580 suites ±0     108 💤 +1 
  580 files   ±0       0 ❌ ±0 

Results for commit d335eff. ± Comparison against base commit f00dd3f.

This pull request skips 1 test.

com.wire.kalium.logic.feature.conversation.ObserveConversationInteractionAvailabilityUseCaseTest ‑ givenProteusConversationAndUserSupportsOnlyMLS_whenObserving_thenShouldReturnUnsupportedProtocol[jvm]

♻️ This comment has been updated with latest results.

[github-actions]

Bencher Report

Branch	fix/message-composer-is-blocked-when-the-user-have-1-mls-client-after-migration-cherry-pick
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 CLI flag.

Click to view all benchmark results

Benchmark	Latency	microseconds (µs)
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInFiles	📈 view plot ⚠️ NO THRESHOLD	680.86
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInMemory	📈 view plot ⚠️ NO THRESHOLD	323,951.00
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.messageInsertionBenchmark	📈 view plot ⚠️ NO THRESHOLD	1,334,663.28
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.queryMessagesBenchmark	📈 view plot ⚠️ NO THRESHOLD	21,441.69

🐰 View full continuous benchmarking report in Bencher

[datadog-wireapp]

Datadog Report

Branch report: fix/message-composer-is-blocked-when-the-user-have-1-mls-client-after-migration-cherry-pick
Commit report: ca93db5
Test service: kalium-jvm

✅ 0 Failed, 3276 Passed, 108 Skipped, 1m 1.1s Total Time

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 56.00000% with 11 lines in your changes missing coverage. Please review.

Project coverage is 54.12%. Comparing base (f00dd3f) to head (d335eff).
Report is 1 commits behind head on develop.

Files with missing lines	Patch %	Lines
...um/logic/feature/conversation/ConversationScope.kt	0.00%	6 Missing ⚠️
.../com/wire/kalium/logic/data/user/UserRepository.kt	0.00%	3 Missing ⚠️
...serveConversationInteractionAvailabilityUseCase.kt	91.66%	1 Missing ⚠️
...ire/kalium/persistence/dao/client/ClientDAOImpl.kt	75.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #3204   +/-   ##
========================================
  Coverage    54.11%   54.12%           
========================================
  Files         1264     1264           
  Lines        36818    36829   +11     
  Branches      3738     3738           
========================================
+ Hits         19925    19934    +9     
- Misses       15451    15454    +3     
+ Partials      1442     1441    -1     

Files with missing lines	Coverage Δ
...om/wire/kalium/persistence/dao/client/ClientDAO.kt	100.00% <ø> (ø)
...serveConversationInteractionAvailabilityUseCase.kt	90.90% <91.66%> (+8.30%)	⬆️
...ire/kalium/persistence/dao/client/ClientDAOImpl.kt	78.33% <75.00%> (+3.33%)	⬆️
.../com/wire/kalium/logic/data/user/UserRepository.kt	67.44% <0.00%> (-0.60%)	⬇️
...um/logic/feature/conversation/ConversationScope.kt	0.00% <0.00%> (ø)

... and 3 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 f00dd3f...d335eff. Read the comment docs.