The user may need to create new CC API credentials because they may have been compromised.
This can be done by simply deleting the secret containing CC API credentials, which is then recreated by the CO.
The problem is that CC is not restarted, which leads to the following Rebalance error:

```sh
2024-01-29 17:44:08 ERROR KafkaRebalanceAssemblyOperator:483 - Reconciliation strimzi#64(kafkarebalance-watch) KafkaRebalance(test/my-rebalance): Status updated to [NotReady] due to error: Unexpected status code 401 for request to my-cluster-cruise-control.test.svc:9090/kafkacruisecontrol/rebalance?json=true&dryrun=true&verbose=true&skip_hard_goal_check=false&rebalance_disk=false
```

To fix this issue, I'm adding the API secret hash as CC annotation, so that any change will trigger a CC pod restart.

Signed-off-by: Federico Valeri <fedevaleri@gmail.com>

Signed-off-by: Federico Valeri <fedevaleri@gmail.com>

Signed-off-by: Federico Valeri <fedevaleri@gmail.com>

Signed-off-by: Federico Valeri <fedevaleri@gmail.com>

Signed-off-by: Federico Valeri <fedevaleri@gmail.com>

Signed-off-by: Federico Valeri <fedevaleri@gmail.com>

Signed-off-by: Federico Valeri <fedevaleri@gmail.com>