The container name is now stored as an attribute on the Heptapod
instance, and it's been a good opportunity to centralize docker calls
there.

Since we're not mentioning docker at all in the API,
this is also a step towards running these tests
on a source install of Heptapod: it wouldn't be hard to implement
them with subprocess and direct filesystem manipulations.