Seemingly indefinite wait at a get operation

[shawkins]

A get operation failed to complete, far exceeding the default request timeout - which is not directly enforced by OperationSupport.waitForResult. There's an assumption that the httpclient layer will enforce the timeout. However if okhttp has exhausted it's max requests, it will not enforce the timeout while the request is enqueued. We have seen this as an issue with websockets, which for some reason count against the request total - so watches / informers will eventually exhaust the max requests.

Two changes are possible here - some enforcement of the request / read timeout in waitForResult, and take responsibility in the okhttp httpclient logic for incrementing the max requests for long running requests (websockets, even http watches if possible, but that seems more difficult to detect).