Re-enable Cassandra 4.0 in CI and fix failing tests

[adutra]

We must re-enable Cassandra 4.0 and fix all the partitioner tests. They are currently failing with 4.0 for unknown reasons.

┆Issue is synchronized with this Jira Task by Unito

[adutra]

It turns out it could be a problem with how CCM is enabling vnodes in Cassandra 4.0. Upgrading the ccm version might solve it.

[adutra]

Confirmed that the problem is vnodes:

ccm create ccm1 -i 127.0.0. -n 3 -v 4.0.1 --vnodes
ccm start
ccm node1 nodetool status

Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address    Load       Tokens  Owns (effective)  Host ID                               Rack
UN  127.0.0.2  73.45 KiB  256     100.0%            b2905481-bdfe-448e-bbb5-eb28781002a6  rack1
UN  127.0.0.1  73.49 KiB  256     100.0%            6a250e50-3c55-4806-91d2-d809c536a3ab  rack1

Observe the broken token ownership and that one node is not showing up at all.

The public version of CCM does not have the issue, but the private version used at DataStax does. We are working on updating our Docker images to use the public version.