apiv2: timeout

[bkendall]

Description

This introduces a new timeout option to apiv2. This can (and should) be used rather than providing signal controllers and managing that logic in other places.

I updated an existing spot (proxying traffic through Hosting emulator) that used a signal to use the timeout instead. I also updated the project management API for listing projects to use the new timeout mechanism in the new apiv2 (this ended up requiring updating a bunch of tests - and for kicks, nock - but I think it was worth it).

Interesting decision I made: I did not expose timeout on the verb methods. Looking at the type definitions, I couldn't convince myself that VerbOptions was correct. Maybe putting it in ClientHandlingOptions would work (since that ends up being an extension of other options), but I wasn't thrilled with that since it's an option of the request, not the handling of it. Up for opinions, but it's not too much of a hassle to change later either.

Scenarios Tested

• Making a request to the Hosting emulator proxying to a function that takes too long, when set with a hardcoded shorter timeout.
• Tested projects:list with a hardcoded short timeout to see the failure.

[coveralls]

Coverage increased (+0.05%) to 65.427% when pulling 88bc357 on bk-apiv2-timeout into 8082b68 on master.