Storage backend for stats

This PR is trying to build a starting point for #39.

The storage package is same as in #49. For every container, it sends container stats to a thread/goroutine pool and worker threads/goroutines will then write those stats to some backend storage.
Why a channel and not just a function call to the storage driver?