[test] TestBrokerWithConfig should not rely on strimzi Topic Operator creating KafkaTopic

[maschmid]

Describe the bug
https://github.com/knative-extensions/eventing-kafka-broker/blob/main/test/e2e_new/broker_config_test.go / https://github.com/knative-extensions/eventing-kafka-broker/blob/main/test/rekt/features/broker_config.go#L58

expects KafkaTopic to be created by Strimzi Topic operator based on the kafka topic created via the kafka admin client.

This behavior will not work anymore in new strimzi "Unidirectional Topic Operator", see https://strimzi.io/blog/2023/11/02/unidirectional-topic-operator/ , so the tests should not depend on it.

Expected behavior
TestBrokerWithConfig passes even with new Strimzi "Unidirectional Topic Operator"

To Reproduce

Knative release version
1.11

Additional context
We should disable TestBrokerWithConfig until we find a better way of asserting actual kafka topic configuration from within the e2e test.

There are at least two options:

• Using a kafka admin client from inside the test. This will be problematic, as the e2e test can run outside of the cluster, with the Kafka being deployed inside the cluser (You don't just port-forward to a Kafka cluster... )
• Using something like https://github.com/provectus/kafka-ui , to expose kafka cluster metadata that could be exposed to the e2e test running externally.