Assorted fixes to get Chicago GTFS to load.

*  Increase various timeouts
*  Bump memory (scala needed 7GB to calculate Chicago's indicators)
*  Add println statements to indicator calculations, for debugging

@echeipesh is looking into scala logging frameworks.

To get the Chicago GTFS to load, I modified it to add `agency_id` entries, as a temporary workaround for azavea/gtfs-parser#2 .
Yeah, I think @notthatbreezy has it right -- the request-timeout is triggered if the actor that is spawned to handle the request doesn't return a response within that period of time. So the handler for the post request needs to spawn another actor that does the actual calculation, and then immediately return a 201 or whatever.