Right now, the Connect builds are using the same operation timeout as all other operations. But in some cases, the Kafka Connect builds can take a long time - especially if they download lot of connectors or when they have slow connection for downloading artifacts / pushing images. Currently, when the build fails to finish within the timeout, it is deleted and a new build is started in the next reconciliation. So a user with a slow build has only one option - increase the operation timeout. But that increases the timeout for all operations, so it is not optimal.

As a first step, we should add a new timeout dedicated to the Kafka Connect builds. It should default to 5 minutes (same as the operation timeout) and not be set by default since in most cases it should not be needed. But it can be increased if needed.

In a long term, we should in addition to the timeout (which in my opinion makes sense anyway since when it runs over the timeout it errors the reconciliation which can be avoided with the timeout) also change the build process to not start new build every reconciliation but follow on the build left over from previous reconciliation. But this is more complicated to implement and it is not done in this PR which adds only the new timeout. This is covered in issue https://issues.redhat.com/browse/ENTMQST-2513.