WIP: Prototype Redis Sentinel implementation

Handles connect lookup. Tested connection in simple & working,
local setup. No automated tests. No fancy sentinel interation (failover
and friends). No documentation. No reconnects were tested (but should
work).

The Redis Sentinel client guidelines leave unspecified whether or not
the connection to the Redis Sentinel should be kept alive. This
implementation currently doesn't. I'm in two minds about this.

IDONTKNOW needs to be handled differently. If ANY Sentinel says
IDONTKNOW to a master resolution request, we need to bail.
Tentatively correct "Sentinel replying IDONTKNOW" handling
Implement other sentinel subcommands and sentinel autoupdate
don't include logs in git
now we can test redis Sentinel. fixed some various typos
use diag
fix test
don't use confess, use croak instead
reimplement Sentinel support
doc
documentation
Clarification for (p)unsubscribe commands.

it seems that unsubscribe/punsubscribe needs reference to previous callbacks
Fixes #69
PP Redis protocol parcer implementation based on sysread
try to get a cnx timeout
Merge pull request #71 from celogeek/master

try to get a cnx timeout
use Test::TCP for cnx_timeout test
Merge pull request #72 from celogeek/master

use Test::TCP for cnx_timeout test
Merge pull request #70 from vsespb/unsubscribe_docs

Clarification for (p)unsubscribe commands.
use Net::EmptyPort to get a free port. Some phrasing fixes
emphasis even more