feat: better error message when transaction to command topic fails to initialize by timeout

[stevenpyzhang]

Description

Addresses #4453

Moved transactionalProducer.initTransactions() out of the same try catch block as the rest of the transaction operations.
Added more specific error message. (added as a pluggable one for scenarios where it doesn't make sense to advise the user to set their Kafka configs)

This isn't ideal currently as there are other reasons for a TimeoutException to be returned from initTransaction but until https://issues.apache.org/jira/browse/KAFKA-9511 is worked on, I think this is the best we can do.

Testing done

Unit test
Spun up a Kafka without setting the required configs, got the error message when issuing a DDL to the server.

ksql> CREATE STREAM source_ab (myFixedField1 varchar, eventPayload varchar) WITH (kafka_topic='topic_a', PARTITIONS = 1, value_format='json');
Timeout while initializing transaction to the KSQL command topic.
If you're running a single Kafka broker, ensure that the following Kafka configs are set to 1:
- transaction.state.log.replication.factor
- transaction.state.log.min.isr
- offsets.topic.replication.factor

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[agavra]

LGTM! Nice error message

[rmoff]

Thanks for fixing this. One small comment:

If you're running a single Kafka broker, ensure that the following Kafka configs are set to 1:

Might be slightly better (less ambiguously) worded:

If you're running a single Kafka broker, ensure that the following configs are set to 1 on the broker: