Since SinkConfig is a namedtuple now, several of the methods we had been
testing are now inherited from tuple.  There's no need for me to test
those here, so I've removed the unneeded test cases.

Rather than having one method doing double-duty as getter and setter,
with ugly syntax, why not use a property?  Now the Sink's output can
simply be read and written as a boolean.

The README has been updated to show how to manipulate the new SinkConfig
objects, as well as what the output really looks like now.

Since it's a class used for little more than storage, with no
interesting non-magic instance methods, it makes sense for SinkConfig to
be a namedtuple.  The rest of its code was mostly just boilerplate,
after all.  What remains makes it do everything we need with only slight
changes to its behavior (most notably, SinkConfig must be instantiated
with all its arguments now).

Any command sent with send_command could be invalid.  It makes sense for
that method to throw an exception if the command isn't recognized so I
don't have to duplicate that effort in the methods for all commands
introduced after firmware version 1.0.  This commit moves the command
validity checking to Sink.send_command.

Now when the `output` command is unsupported by the Sink, the library
raises a different exception than if unknown text is printed.  This
allows feature testing, which is great.

Sink.output provides a Pythonic interface to the PD Buddy Sink's output
command.

They're now right next to boundary values, which is much more reasonable
than the arbitrary values they had before.

Added code to set_v and set_i to check if the Sink gave any error
message when running those commands, raising exceptions if it did.
This makes two of the three new tests pass.  The other one will need
support from the Sink itself, which currently doesn't care if the
voltage is over 20 V or the current is over 5 A.  That is to say that
the third test will automatically start passing if the Sink is running
firmware 1.0.1, which is yet to be released.

Added three new tests: test_set_tmpcfg_huge, test_set_tmpcfg_big, and
test_set_tmpcfg_neg.  They set temporary configurations with huge
(> UINT16_MAX), big (> 20 V, > 5 A), and negative voltages and currents,
respectively.  These tests all fail currently, so I'll work on making
them pass.

Whoops!  The version that was pushed to PyPI is correct, but I forgot to
commit the change.

The library has now been tested with Python 2.7, 3.3, 3.4, 3.5, and 3.6.
The README and setup.py now indicate this.  The README also says how to
run the tests, and that you need a PD Buddy Sink plugged in for them to
be completely thorough.

It's at 100% branch coverage.  Woohoo!

May change before the real 0.1 release, but this allows easier test
coverage measurements.

100% statement coverage for the SinkConfig class, except for __repr__
which is mostly for debugging anyway.

Before, we sent ^D, but didn't read past the prompt that appeared.  This
put us one command behind the most recent, causing all manner of mayhem.
It's all fixed now I believe, but this really shows the need for unit
testing.  I'm working on that.

This removes any garbage that the Sink may have in its buffer, e.g.
partially entered commands or nonsense that appeared when moving the
device to/from a VM.

One extra dependency is pulled in for Python versions older than 3.6,
but other than that it's pretty easy to support them.  It definitely
works on 2.7 now, and should work on older 3.x versions (but that's
untested).

It would've crashed before, but now it returns "No configuration" like
the command shell does.

Now the port is not part of the API, there's a method to close it,
__init__ can take a string in addition to the objects it used to take,
and the class is a context manager for the with statement.  I can
confidently say that these are all great changes.

It's the preferred format for Python, after all.

It returns the SinkConfig in the standard format, just like the serial
configuration interface.

The timeout was a dirty hack from the start.  It was long enough that
commands have finished running by the time it completes, but it wasn't
the right way to see when a command finished running.  The right way is
to look for the PDBS) prompt, which is what we do now.

This makes the Sink.set_tmpcfg method run noticeably faster.  Neat.

We use some 3.6-specific features from the enum library, so older
versions won't work.