CC Task initiated too fast in case of volume addition

[baluchicken]

Describe the bug
CC Task initiated too fast in case of volume addition.
In case of a volume addition, the CC task initiated before the volume is bounded to the pod. It causes a false picture of a cluster since the user can think that the rebalance happened successfully but it is not. The rebalance indeed happened successfully but on a broker which is not aware of the new volume.

Steps to reproduce the issue:
Create a KafkaCluster using SimpleKafkaCluster
Wait until CC is operational
Add an additional volume to the default brokerConfigGroup
Check that the GracefulDiskRebalanceSucceeded status populated before the pod even restarted to bound the new volume.

Expected behavior
The Rebalance task in CC should happen after the pvc is bound to the given pod.