Log what peer failed clock-sync

When a peer isn't running to perform a clock-sync, we should log which one it
was.
Improve logging for vnode

Prepend the host, port and partition in front of all log messages in
skuld.vnode
Add more logging for node
Catch netty client exceptions
Log what vnode the claim was trying to happen from
Add more logging
Don't print stack trace for connection refused
Add log message for wiping vnode
Log the task count per partition

This will give more info for tracking down #77.
Merge branch 'quiet-netty-client-exceptions' into improve-logging-for-vnode
More logging cleanup

* Ensure client connection refused messages are shorter in the logs.
* Make all node log messages have the host and port prefix
Fix deadlock in shutdown

If AAE requests and an election is occuring at the time of a shutdown, it can
cause a deadlock in the tests.
Prevent claims to follower vnodes

If a vnode has recently lost its leadership, the node queue may have IDs that
are no longer relevant.

This adds a check to skip any task that belongs to a vnode where this node
isn't the leader.
Fix boolean logic
Improve log message
Add logging of claim requests to peers
Merge pull request #79 from eric/prevent-claims-to-follower-vnodes

Prevent claims to follower vnodes
Merge pull request #78 from eric/fix-deadlock-in-shutdown

Fix deadlock in shutdown
Merge pull request #69 from eric/log-peer-for-clock-sync-exceptions

Log what peer failed clock-sync
Merge pull request #71 from eric/improve-logging-for-vnode

Improve logging to aid in debugging transient issues