Time restrict network operations

[infeo]

Closes #3113

This PR adds to all network requests the timeout parameter, in order to detect and handle "no connection possible" events. It adds the time out to the request itself. For the authentication, this is not possible over the API, hence, only a connect timeout is set.

The timeout varies between 3 and 5 seconds.

[SailReal]

I would recommend increasing the timeout to at least 10 seconds. If we think of a bad hotel or "Deutsche Bahn" WiFi, the user is connected to the corporate VPN and then wants to perform an unlock on a stressed hub server, giving up after 3 seconds is way too early in my opinion.

The default of OkHTTP is 5s for connect, read, write and 10s for the hole call (including DNS etc):

• https://github.com/square/okhttp/blob/2344b87c59456088ed1346221d45648634f7f0c8/samples/guide/src/main/java/okhttp3/recipes/kt/ConfigureTimeouts.kt#L24-L27
• https://www.baeldung.com/okhttp-timeouts

[SailReal]

👍 LGTM but because of

This does not add a timeout to the timespan between start of the Auth Flow and its fulfillment (i.e. redirecting back to the app).

(from coffeelibs/tiny-oauth2-client#5)

this does not fully solve the motivation of #3113

This can confuse users due to missing feedback/endless response waiting, especially, if different applications with explicit proxy settings have internet access.

because it is still true that if the server takes infinitely long to respond (e.g. no internet connection) Cryptomator waits forever for the response while trying to unlock a Hub vault.

So I think we should add a timeout waiting for the redirect as well, but if you prefer we can do that in another PR later.