Timeouts should be configurable

[ColinSullivan1]

When testing against SaaS providers, benchmark setup can take quite a bit of time. If actions such as topic creation are artificially throttled it can take upwards of 20 minutes to create hundreds of topics, consumers, etc.

In order to support this, the HTTP worker timeouts (read/request) should be configurable.

The line with hardcoded timeout is here:

benchmark/benchmark-framework/src/main/java/io/openmessaging/benchmark/worker/HttpWorkerClient.java

Line 61 in fe3c5a0

this(asyncHttpClient(Dsl.config().setReadTimeout(600000).setRequestTimeout(600000)), host);

The workers creating the topics could periodically return a status and the benchmark orchestrator could timeout upon missing a few status updates, but the low hanging fruit would be making these values configurable.