Analytics logging in edge-case scenarios

[GUI]

If a request to an API backend times out (after 60 seconds by default), the entries in the analytics system for those requests seem to be missing the details on the api_key and user of the requester.

[GUI]

(Renaming this issue to be broader and inclusive of the issues we've also seen in #106)

As a quick update on this issue, I've been working on a bit of an overhaul in how we coalesce our analytics data on API requests. The new approach simplifies the code, ensures we log things properly in a variety of edge-case scenarios where we're missing data, and also makes it much easier to recover the analytics if something goes terribly wrong and the system can't perform it's logging temporarily. It's also faster, more efficient, and gets the analytics into the system more quickly. More integration tests have also been added to test these various edge-case scenarios.

So all-in-all, I think this analytics update is shaping up nicely and will bring more sanity to one of the odder bits of code in the system. I just need to complete some load testing and do some more checks, and then I think we can schedule this for an upcoming update to the platform.

The code is currently sitting in the beanstalk-logs branches of the gatekeeper and router.