Started by Strimzi#9447

As per proposal, the ZooKeeper to KRaft migration process can be rolled back during the migration phase itself or when the cluster is migrated but still in "dual-write" mode.

The user should be able to apply the strimzi.io/kraft: disabled annotation in order to come back to use the cluster as ZooKeeper-based again and deleting the KRaft controllers.

More additional information about what should be done from a Kafka perspective can be found here https://github.com/apache/kafka/pull/14160/files#diff-e4e8d893dc2a4e999c96713dd5b5857203e0756860df0e70fb0cb041aa4d347bR3786