CommandHandler notifications called out of order

[mp911de]

In some cases, event notifications for reconnection CommandHandler are called out-of-order.

Adding a command handler id makes visible what's going on:

1. The channel is deactivated
2. The channel is reconnected
3. The channel receives an activation
4. The channel is unregistered (notification from the previous channel I/O)

2016-07-23 20:58:54 [DEBUG] [lettuce-nioEventLoop-6-1] [CommandHandlerId 0x31e, /127.0.0.1:36367 -> localhost/127.0.0.1:6479] deactivating channel handler (CommandHandler:708)
2016-07-23 20:58:54 [DEBUG] [lettuce-nioEventLoop-6-2] [CommandHandlerId 0x31e, (inactive)] channelRegistered() (CommandHandler:113)
2016-07-23 20:58:54 [DEBUG] [lettuce-nioEventLoop-6-2] [CommandHandlerId 0x31e, /127.0.0.1:36371 -> localhost/127.0.0.1:6479] channelActive() (CommandHandler:583)
2016-07-23 20:58:54 [DEBUG] [lettuce-nioEventLoop-6-1] [CommandHandlerId 0x31e, /127.0.0.1:36371 -> localhost/127.0.0.1:6479] channelInactive() done (CommandHandler:733)
2016-07-23 20:58:54 [DEBUG] [lettuce-nioEventLoop-6-1] [CommandHandlerId 0x31e, /127.0.0.1:36371 -> localhost/127.0.0.1:6479] channelUnregistered()