Inform about reverted scale-down or role-change in .status section

[scholzj]

Type of change

• Enhancement / new feature

Description

Currently, when we revert a scale-down or role change because the brokers are not empty, we just log warning in the log. This PR adds this also as a warning condition to the custom resource to make it easier to see from there as well.

  conditions:
  - lastTransitionTime: "2024-02-11T19:55:53.565162526Z"
    message: Reverting scale-down of KafkaNodePool aston by changing number of replicas
      to 2
    reason: ScaleDownPreventionCheck
    status: "True"
    type: Warning
  - lastTransitionTime: "2024-02-11T19:55:53.605476276Z"
    message: Reverting role change of KafkaNodePool controllers by adding the broker
      role to it
    reason: ScaleDownPreventionCheck
    status: "True"
    type: Warning
  - lastTransitionTime: "2024-02-11T19:55:55.428272506Z"
    status: "True"
    type: Ready

Checklist

• Write tests
• Make sure all tests pass
• Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally

[scholzj]

/azp run regression

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scholzj]

/azp run kraft-regression

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ppatierno]

LGTM