Unpacking of transaction logs occurs right after response deserialization

This PR fixes unpacking of transaction logs that are send with practically all responses. Unread logs remained in netty channels, were read and misinterpreted by next requests.
For example it caused `ArrayIndexOutOfBoundsException` during lock sessions because we did not read all transaction logs during `newLockSession` request and following `acquireLock` request read stale data from channel.