On AWS, Cassandra doesn't come up after restoration - A node with address already exists

[c3-clement]

What happened?

On AWS (EKS and S3 Bucket), the Cassandra Statefulset won't come up sometimes after restoration.
On a K8ssandra cluster with 1 dc of 3 nodes, 2 are not reaching readiness probe.

On failed pods, the following error message is showing up in logs:

java.lang.RuntimeException: A node with address /172.0.238.69:7000 already exists, cancelling join. Use cassandra.replace_address if you want to replace this node.
	at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:749)
	at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:1024)
	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:874)
	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:819)
	at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:418)
	at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:759)
	at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:893)

Did you expect to see something different?

How to reproduce it (as minimally and precisely as possible):

Environment

• K8ssandra Operator version:

  Insert image tag or Git SHA here

• Kubernetes version information:

  kubectl version

• Kubernetes cluster kind:

  insert how you created your cluster: kops, bootkube, etc.

• Manifests:

insert manifests relevant to the issue

• K8ssandra Operator Logs:

insert K8ssandra Operator logs relevant to the issue here

Anything else we need to know?:

[c3-clement]

Duplicate of #1325