refactor: replace NewClientEventData with ClientDTO

[typfel]

---

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

NewClientEventData duplicates ClientResponse since they are represented by same underlaying type.

Solutions

Delete NewClientEventData and replace it with ClientDTO (renamed from ClientResponse) and we can also remove some repeating mapping code due to this.

---

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]

Unit Test Results

   374 files  ±0     374 suites  ±0   2m 0s ⏱️ +40s
1 991 tests ±0  1 909 ✔️ ±0  82 💤 ±0  0 ❌ ±0 

Results for commit 47c32c3. ± Comparison against base commit ed3bdbb.

♻️ This comment has been updated with latest results.

[MohamadJaara]

does the new client event also include ?

    @SerialName("mls_public_keys") val mlsPublicKeys: Map<String, String>?

[typfel]

Yes, but it's always empty because the mls keys are always added after a client has been created currently.

[MohamadJaara]

LGTM