Cluster stateful set stuck when failed scheduling occurs

If there exists a cluster and the resource requests are scaled up resulting in failed scheduling, that cluster node will be stuck in a failed state, even in resource requests are reduced.

The flow looks like:

1. Scale up cluster nodes
2. Last node in stateful set will be updated
3. Node fails to schedule
4. Reduce the resource requests for the `CrdbCluster`
5. Stateful set is not updated to reflect new resource requests

The workaround is that the cluster admin or whoever with access must manually edit the stateful set to assign the updated requests.