Support manual storage expansion with rolling replacements

[tnozicka]

When there is no more space on the same nodes we need a procedure to change the storage request and replace node 1 by 1. (This assumes all the ScyllaDB nodes run on similar nodes so it's most likely to be group operation + we already have a single node replacement.)

- [ ] https://github.com/scylladb/scylla-operator/issues/732
- [ ] https://github.com/scylladb/scylla-operator/issues/1573
- [ ] https://github.com/scylladb/scylla-operator/issues/1574

[scylla-operator-bot[bot]]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[tnozicka]

/remove-lifecycle stale /triage accepted