WiP - Initial commit of a Hoard/Whisper direct backend
Fixes concurrent whisper file creations under heavy load
New approach to flushing out the stats at irregular intervals
Move from hoard to ceres
Updated to new namespace style of StatsD stats.
update to handle new logging style
Addresses potential data loss issue

The code was a bit racey, in particular around the clearing down of the
values 'queue'.  I *think* that it was possible that a node's write
could complete and clear down metrics that hadn't actually been pushed
down to the ceres back end.

Also removed the overlapping setInterval call as it doesn't seem neccessary.
Add a temporary file flusher for diagnostics
Adds experimental timestamp clamping

Basically attempts to address issues with 'clock jitter' when the
flushes are occurring around flushinterval boundaries.

Fairly rough first go, that will not cope with date/time changes on the
machine (effectively an absolute time is calculated once, and incremented
for each flush!)
Updated ceres backend

* Now ceres nodes are created with the correct schemas etc.
* New rollup maintainence task that executes at 12:05 every night
Towards production ready, depend on ceres as a library, not a local folder
Stop losing time :/

* There was a problem where a sequence of extremely slow flushes to ceres
caused the clamped timestamp to drift backwards.
* I've decoupled the actual flushing, from the request-to-flush from statsd.
* Hopefully this means in this scenario all that should happen is that the
flushes take a bit longer when catching up, but the time series data won't be lost.