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.
Do you mean the tupled/unapply portion? That's a shortcut that works because those are methods on the companion object automatically generated for the case class. Those methods do exactly like they sound what they do -- go to/from case class and tuples.

That works fine when the case class is just primitive data types that correspond directly to database types. In this case, the case class actually has other objects (`SamplePeriod`, etc.) in it. You can provide any function that maps to/from tuples to case class - which is what is going on here. The transformation from database values -> case class in this instance is necessary, but actually kind of broken. We don't use it anywhere, and to make it useful would require adding an additional table for sample period. If this ever gets used, this will need to be fixed; but in the interests of time I left it as a todo.