Port to libchan, pt. 1

This is a minimal effort to get things running. Only the `beam` package
has changed - backend code is untouched.

- The `beam` package is still around, but functions as a
  libswarm-specific wrapper around libchan messages. It'll either be
  renamed or moved to the top-level namespace.

- We have our own Message type which serializes/deserializes to libchan
  messages, and our own versions of Sender and Receiver which speak
  libswarm. WrapSender and WrapReceiver promote libchan objects to
  their libswarm equivalents.

- We also have our own wrappers around libchan utilities: RetPipe,
  Handler, Pipe, Copy.

Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
Basic tests for Message/Sender/Receiver

Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
Add maintainers for individual backends

Signed-off-by: Solomon Hykes <solomon@docker.com>
Merge pull request #91 from aanand/port-to-libchan
Implement NopSender (removed by switch to libchan)

Signed-off-by: Solomon Hykes <solomon@docker.com>
Fix debug after switch to libchan

Signed-off-by: Solomon Hykes <solomon@docker.com>
Merge pull request #93 from shykes/pr_out_fix_debug_after_switch_to_libchan
Merge pull request #88 from shykes/backend-maintainers
Fix Debug for Libchan

This includes some minor cleanup among other things needed to make debug work with libchan (correctly).

Signed-off-by: John Hopper john.hopper@jpserver.net