fix port to host assignments in connection strings

[supersven]

The rules:

• If there is no port field, use the default for all hosts
• If there is exactly one port value, use it for all hosts
• If there are more than one port values, they are matched 1:1 to the hosts (counts must match!)
• port1, means port1,<default>, ,port2 means <default>,port2, port1,,port3 means port1,<default>,port3

Port / host mappings can fail now. Express this with MonadFail.

N.B. only 9780828 is a candidate for upstreaming as fromKeyValueParams doesn't exist upstream.

wire-server currently follows a feature branch: https://github.com/wireapp/wire-server/blob/a1fb9bc0a6fdaa8d286f8d0b25cfe6e0572b22ba/flake.lock#L350-L366 So, this won't break it now, but callers of fromKeyValueParams need to be adjusted once the followed branch is switched there.

Ticket: https://wearezeta.atlassian.net/browse/WPB-27405

---

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

Briefly describe the issue you have solved or implemented with this pull request. If the PR contains multiple issues, use a bullet list.

Causes (Optional)

Briefly describe the causes behind the issues. This could be helpful to understand the adopted solutions behind some nasty bugs or complex issues.

Solutions

Briefly describe the solutions you have implemented for the issues explained above.

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.

[akshaymankar]

Looks good!