fix(mls): fetch and set mls-removal keys for 1on1 conversations (WPB-10743) 🍒 🍒

[github-actions]

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

• fix(mls): fetch and set mls-removal keys for 1on1 conversations (WPB-10743) 🍒 #3021

Original PR description:

---

WPB-10743 [Android] Use proper MLS removal key with federated 1:1 conversations

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

• fix(mls): fetch and set mls-removal keys for 1on1 conversations (WPB-10743) #3020

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?

Fetch and set removal-keys from the get-oneonone-conversation response for 1on1 conversations and only APIV6

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.

[sonarcloud]

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 SonarCloud