Minor Description
Created after PR discussion here.
In some of our integration tests, we want to verify that a Connect worker cannot start under poor conditions (such as when its internal topics do not yet exist and it is configured to create them with a higher replication factor than the number of available brokers, or when its internal topics already exist but they do not have the compaction cleanup policy).
This is currently not possible, and presents a possible gap in testing coverage, especially for the test cases testFailToCreateInternalTopicsWithMoreReplicasThanBrokers and testFailToStartWhenInternalTopicsAreNotCompacted. It'd be nice if we could have some way of synchronously awaiting the completion or failure of worker startup in our integration tests in order to guarantee that worker startup fails under sufficiently adverse conditions.
