Add config parameter for request timeout

[bartek]

We use requests internally to make calls out to the G API. By default, requests has no timeout defined, and it's up to the backend source to define when it'll give up. Currently we have a backend time out of 60 seconds, primarily due to resources like the bundler.

Requests greatly encourages we set a reasonable timeout and use it in every production call [1]

You can tell Requests to stop waiting for a response after a given number of seconds with the timeout parameter. Nearly all production code should use this parameter in nearly all requests. Failure to do so can cause your program to hang indefinitely:

This should be added as a configurable parameter, with a reasonable default (20 or 30 seconds seems more than enough)

1. http://docs.python-requests.org/en/master/user/quickstart/#timeouts

[jonprindiville]

Oh, yeah, actually I was thinking about gapipy timeouts recently as well.

@marz619 you know if anybody else is clamouring for this kind of feature? (I suspect "no" based on age and status of this issue 🙃)

Some examples I find when Googling for stuff like "python requests timeout" involve subclassing HTTPAdapter and having it include a timeout in every send call...

I suppose that could be possible here as well, but we could also achieve a similar effect, I think, by just including some timeout whenever we APIRequestor._make_call -- might be a better place for it, that's just where my cursory looking around lead me.