Cannot set timeout option for Guzzle through the client

[dbauer91]

In the current implementation, I am not able to set a timeout for HTTP requests. As Guzzle defaults its request timeout to 0 (i.e., indefinite) errors in certain cases cause indefinite execution of synchronous code, waiting for some action to complete, that is yet to be determined on my end.

Nevertheless, having the option to set a timeout for this client's requests is not only a band-aid to get important functions to work again over here, but also an option that, I think, is useful in general.

Criticism is absolutely welcome!

All the best,
Dirk