agent: use harpoon-supervisor

The primary goal of this PR is to get harpoon-agent using the new harpoon-supervisor instead of harpoon-container.

With that in mind, I've attempted to limit the changes (behavioral, code) to the agent; we already have other issues which can address this (e.g., #8 and #54), and it would be nice to have all new code using the supervisor sooner rather than later.

Implements #48.
Can we end up in a state where dial continually returns ENoENT?  (I think so, if the supervisor dies before creating the socket.) If so, should there be an appropriate exit strategy ala ECONNREFUSED?