Fix cql-io bug where restarting C* cluster could cause downtime

[akshaymankar]

Upstream changes in https://gitlab.com/twittner/cql-io/-/merge_requests/20

JIRA: https://wearezeta.atlassian.net/browse/SQCORE-1345

Checklist

• The PR Title explains the impact of the change.
• The PR description provides context as to why the change should occur and what the code contributes to that effect. This could also be a link to a JIRA ticket or a Github issue, if there is one.
• changelog.d contains the following bits of information (details):
  • A file with the changelog entry in one or more suitable sub-sections. The sub-sections are marked by directories inside changelog.d.

[akshaymankar]

Please approve this PR only if you approve of the upstream MR.

[fisx]

why is this added here? don't mind either way, just surprised.

[akshaymankar]

I just ran the script in tools/convert-to-cabal to keep stack.yaml and cabal.project in sync. I was confused too, but then thought maybe someone added some dependency and forgot to run that script.

[jschaul]

Is it possible to create a test for this behaviour before/after; or is that not so easy? If not, would it be possible to detail the manual test procedure steps either here in wire-server in some docs; or in the MR upstream on how you tested the change? (internal jira comments can't be read by cql-io maintainers or anyone else interested)

[akshaymankar]

Is it possible to create a test for this behaviour before/after; or is that not so easy? If not, would it be possible to detail the manual test procedure steps either here in wire-server in some docs; or in the MR upstream on how you tested the change? (internal jira comments can't be read by cql-io maintainers or anyone else interested)

I think it is quite hard to create an automated test for this since it requires talking to kubernetes. I wrote about my method of testing in the upstream MR: https://gitlab.com/twittner/cql-io/-/merge_requests/20#note_1074472850