Lay groundwork for RESP3 support and flat ChannelHandler hierarchy

## Motivation

Since Redis 6.0, a new serialization protocol format (v3) is available that gives richer semantic reasoning behind the different types to enable commands to better understand the return types to provide in their programming language.

In addition, the `RESPTranslator` type is going to see more direct usage, and the current API doesn't make read well.

## Changes

- Add: Internal `RESPVersion` enum that the `RESPTranslator` will start to use
- Rename: `RESPTranslator.parseBytes` to `RESPTranslator.read(from:)`

[Misc] Update contributors

Allow nightly trunks CI jobs to fail

Backdeploy #100 fix and deprecate Channel Redis pipeline APIs

This is a backdeploy of commit cfb99ba.

This fixes issue #100

#103 -- Provide error in unsubscribe pub/sub handler if available

92 -- Accept event loop and logger in RedisClient commands

There are many times that developers want exact control over which EventLoop will be executing their chained EventLoopFuture callbacks
and which Logger will do the logging in calls deep within RediStack.

All commands will now accept an optional EventLoop and Logger to hop to, and using the logger for desired logs.

92 -- Accept event loop and logger in RedisClient commands

There are many times that developers want exact control over which EventLoop will be executing their chained EventLoopFuture callbacks
and which Logger will do the logging in calls deep within RediStack.

All commands will now accept an optional EventLoop and Logger to hop to, and using the logger for desired logs.

104 -- Use correct base method for zrevrange overload methods

102 -- Remove usage of deprecated NIO ELF APIs

95 -- Backport unexpected channel closure callback

This is a cherry-pick commit of ad316a9