Abstract GUIDs. Properly support unicode GUIDs.

### Motivation:
PR #686 implements `__eq__` for `node/connection.py::CryptoPeerConnection`. The implementation was borrowed from that of `node/contact.py::Contact`, which was deleted in the said PR. However, the implementation was not correct: it mishandled the case where `unicode` GUIDs are used. This PR fixes that. It also abstracts the GUID out of `CryptoPeerConnection` into a separate file.
  
### Changelog:
* Factor `AbstractGUID` out of `node/connection.py::CryptoPeerConnection` and `test/test_kbucket::AbstractGUID`.
* Add `unicode` support. 
* Supply a complete testsuite for the new class.
* Fix relevant documentation
The object is really just a string to begin with isn't it? Are we getting a little crazy with the abstraction here? A GUID is simply a ripemd160 hash string. What are we getting by abstracting this out to it's own object?