Feature/save-indicators-from-scala

This commit changes how indicators are save to the
database by saving results directly to the database
via scala. Prior to this commit, results were sent
over the wire to django, which then had to read the
response and then save the results to postgres.

Django could not keep up with saving, serializing,
and deserializing many geometries in quick succession.
This would then lead to timeouts and failures for
indicator processing.

Saving results directly to the database bypasses
this problem.

Also fixes a bug where translations for formatted values were not working correctly.
I thought that with case classes you could do something similar to how it's done here: https://github.com/WorldBank-Transport/open-transit-indicators/blob/develop/scala/gtfs/src/main/scala/com/azavea/gtfs/io/database/StopsTable.scala -- does that not work in this case?