cassandra/docker-compose: go back to using the latest cassandra version

[cvybhu]

In January the tests started failing on Cassandra 4.1, so we pinned the cassandra version to 4.0.7, which didn't have these problems. 4.0.7 is the version that we've been using in the CI since then.

In the meantime there were new releases of Cassandra, at the moment the latest is 4.1.3. Let's try to go back to the latest version, maybe the problems fixed themselves during the last nine months.

Refs: #620
Refs: #629

Fixes: #633

Pre-review checklist

• have split my patch into logically separate commits.
• All commit messages clearly explain what they change and why.
• I added relevant tests for new features and bug fixes.
• All commits compile, pass static checks and pass test.
• PR description sums up the changes and reasons why they should be introduced.
• I have provided docstrings for the public items that I want to introduce.
• I have adjusted the documentation in ./docs/source/.
• I added appropriate Fixes: annotations to PR description.

[cvybhu]

I will rebase this pull request a few times to rerun the CI and make sure that everything works with Cassandra 4.1.3

[cvybhu]

I ran the cassandra workflow 10 times and it succeeded every time. It looks like everything works fine with the latest cassandra.

You can view the runs here :https://github.com/scylladb/scylla-rust-driver/actions/runs/6576484163
Click on to expand the list.