The logic here is:
* if we want default behaviour we just configure `<int-redis:message-driven-channel-adapter queue="redisQueus"/>`.
In this case the `JdkSerializationRedisSerializer` will be applied for bytes from Redis message to deserialize `payload`. It is the most common case.
* if we want receive `byte[]` as `payload` we should just add `serializer=""` attribute. This case is very occasional. Maybe just in XD. Of couse, we can add mutually exclusive `receive-bytes="true"` attribute instead, but...
* if we want deserialize `byte[]` to entire `Message` we just should add `expect-message="true"`
* All other cases can be covered via provided custom `serializer`

`enableDefaultSerializer` was introduced by XD. So, we should be really sure in legality of it.
I don't like it, because default is within our implementation and custom is up to provided `serializer`.