Remove filesystem implementation bias from API

Bring the API into line with the IRC discussion, July 17.

There seemed to be a consensus that the API should be dealing with individual containers and collecting together containers and allowing access from other processes should be the responsibility of the caller.

- Remove `Path()` and add `Id()` in `Container` interface. Update description.
- Remove `Load()` and modify `Create()` in `Factory` interface to remove references to path.
    Update description of `Create()`.

The `libcontainer` API deals only with individual `Container` instances, and does not
provide a 'reaccess' method. `Id()` is exposed for diagnostic information.

Docker-DCO-1.1-Signed-off-by: Steven Powell <spowell@gopivotal.com> (github: Zteve)
Hey Steve, I think I understand the motivation. But I still don't understand why this is the best alternative to solve filesystem dependency. I read through the IRC logs and persistence writeup (https://gist.github.com/glyn/e52612085e7e8529ad91). But it talks about multiple concerns for Create(), Recreate(), and Notify().

Let me sync up with vmarmol@ to understand this better before asking more questions.