Remove confusing error message due to timeout/watch

[szuecs]

These error messages coming from glog, but we should delete these log entries, because the behaviour is intended and the client-go timeout works for WATCH, but not for all other API calls.

...
ERROR: logging before flag.Parse: E0808 14:07:03.579958       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
ERROR: logging before flag.Parse: E0808 14:07:33.581389       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)

[mikkeloscar]

Maybe we just drop the timeout on the client-go configuration since it doesn't seem to work anyway 😒

[szuecs]

We have to investigate what happens if we use no Timeout, but the custom Transport introduced in #24