Volume reconciliation loop

Implements a reconciliation loop that tears down volumes that are no longer in use by any pod.

The set of valid volumes are determined by iterating through the list of manifests. The set of active, or mounted, volumes are determined by traversing the root working directory path for any existing volumes. These maps are compared, and if an active volume does not have a match, it is unmounted and removed.

This allows a kubelet to properly remove mounted volumes and clean up after itself in the event of a crash/restart.
Are volumes uniquely identified such that a later create action would not need to block on a teardown (asking, I don't have a good feel for the code)?  Or in the event a pod is created, removed, then reappears in etcd, must teardown be executed before the next create?