Add series_calc and setup tests
Add boilerplate config and logging setup
Spike out processing engine

Not factored right, but the basic idea is to have an engine with configurable
handlers.  Engines are responsible for the entry format; handlers are
responsible for converting entry data to the data used by the manager and
terms.  Currently a concise line format is used.

More features and refactoring to come.
Refactor command glue into Command class
Cleanup logging setup (ish)

Well at least the weirdness is localized.  More work will need to be done to
really flesh out the configuration cycle later.
Avoid duplicating data in Term#set_data

The dup turned out to be a rather big time sink for high-volume inputs.  This
achieves the same thing with less garbage.
Make separate setting dimension data and updating slot data

These two operations sometimes need to go together, for instance when linkages
update, but don't always need to.  Making them separate allows for some
controllers to drastically speed up their operation by only updating slot data
as needed.
Make SumGraphController follow a 24hr window
Move definition of dimension types to controller

Placing them in the config file makes less sense; I anticipate it will be more
commmon to make a single controller designed to work with a fixed set of
dimension types vs making a generic controller designed for variable dimension
types.  This puts full control in the hands of the controller.
Minor cleanup in SumGraphController
WIP