KAFKA-20982: Enable SASL_PLAINTEXT listener on all brokers in docker sanity test fixtures

[mingyen066]

Only broker1 had a SASL_PLAINTEXT listener, but the test topic (1
partition, RF=1) and the group coordinator can land on broker2/broker3,
causing the client to time out (reported in
#22023 (comment)). Add
the listener to all brokers in both isolated and combined mode,
following the existing SSL pattern.

Reviewers: Chia-Ping Tsai chia7712@gmail.com

[mingyen066]

Verified locally by running the docker sanity tests against apache/kafka:4.3.1:

python docker_build_test.py apache/kafka --image-tag=4.3.1 --image-type=jvm --test --kafka-archive=/tmp/kafka_2.13-4.3.1.tgz

Both combined and isolated modes passed, including the SASL flow:

Created topic test-topic-sasl.
Processed a total of 1 messages
...
All tests passed successfully.

[chia7712]

python docker_build_test.py apache/kafka --image-tag=4.3.1 --image-type=jvm --test --kafka-archive=/tmp/kafka_2.13-4.3.1.tgz

This won't trigger the build flow, so it luckily skips the error mentioned in #22054 (comment) :)

Anyway, would you mind fixing it as well?

[mingyen066]

@chia7712 Thanks for catching this! Fixed and verified the full build + test flow:

❯ python docker_build_test.py kafka/test --image-tag=local-verify --image-type=jvm --kafka-archive=/tmp/kafka_2.13-4.3.1.tgz
[+] Building 29.0s (18/18) FINISHED                                     docker:orbstack
 => [internal] load build definition from Dockerfile                               0.0s
...
Time Elapsed: 0:05:58.472633
All tests passed successfully.

[chia7712]

LGTM

[chia7712]

backport to 4.4 branch