K8SSAND-1416 ⁃ e2e test to upgrade from 3.11 -> 4.0

[burmanm]

What happened? We have no test to check if upgrading from 3.11 to 4.0 is automated using cass-operator. We should have such, at the moment we only test if upgrading between 3.11 versions work.

Updating 3.11 to 4.0 is a bit more complex scenario, involving also updating the sstables. This might require more work in the management-api also if the process takes too long (similar to cleanup / terminate).

Did you expect to see something different?

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

Environment

• Cass 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

* Cass Operator Logs:

insert Cass Operator logs relevant to the issue here

**Anything else we need to know?**:



┆Issue is synchronized with this [Jira Task](https://k8ssandra.atlassian.net/browse/K8SSAND-1416) by [Unito](https://www.unito.io)
┆friendlyId: K8SSAND-1416
┆priority: Medium