Pull request objects out of apiRequest and push request context to response building code.

[michael-mclawhorn]

This is a nice precursor to support:
#709

However the greater motivation is to push less of the response building state via apiRequest and more via injection/invocations of the response building code. Keep the jersey code at the response writing layer.

[michael-mclawhorn]

This cleans up a longstanding conceptual piece of pain by isolating the ApiRequest objects from the mechanics of response building. In the event that ApiRequests were being used in a non Jersey container, this would be a critical function for supporting that.

Worth considering is going one level further and taking the ResponseFormat object out of the ApiRequest. It's debatable that there might be cases where the response format would inform query optimizations, so that change may be premature.

[cdeszaq]

Always a good idea to keep layers separated. I'm a fan of keeping the "this is in service of an HTTP request / response" out of the business logic where we can, but agree that the notion of "response format" may be useful, from an optimization standpoint. At the very least, it can always get extracted later, so no need to increase the scope of this issue with it right now.