Federico Valeri

I will open a new PR based on some refactoring we are doing. The fix is currently hosted in #10248.

> we would not be able to see the upper bound (i.e., how many KafkaTopics is TO able to handle in creation and modification) I think the objective here is...

Thanks for fixing the issue. I will try to run again with bs100,lm10 and compare with my test driver results, they should be pretty close.

It's kind hard to compare, because of the input mismatch (n.events vs n.topics), but the results I got seems strange (yellow line up to 300 events). 

Hi @Pinimo, thanks for reaching out. That's not a regression because the RF change is a new feature, and it is working as designed. This is consistent with how Strimzi...

@strimzi/maintainers can we run STs on this? Thanks.

Failed test is unrelated: ```sh [ERROR] io.strimzi.operator.cluster.operator.assembly.KafkaConnectorIT.testConnectorIsAutoRestarted(VertxTestContext) [ERROR] Run 1: KafkaConnectorIT.testConnectorIsAutoRestarted(VertxTestContext) java.lang.AssertionError: Expected: is "RESTARTING" but: was "UNASSIGNED" [ERROR] Run 2: KafkaConnectorIT.testConnectorIsAutoRestarted(VertxTestContext) java.lang.AssertionError: Expected: is "RESTARTING" but: was "UNASSIGNED" [ERROR]...

/packit test --labels regression

@tombentley system tests looks mostly good with the exception of OpenTelemetryST, which is a known issue unrelated to this PR. Let me know if you are good with latest changes....

/packit test --labels regression