[Java] Implement "ArrowBufReadChannel" abstraction and alternate MessageSerializer that uses this

[asfimport]

The current MessageSerializer implementation is wasteful when used to read an IPC payload that is already in-memory in an ArrowBuf. In particular, reads out of a ReadChannel require memory allocation

• https://github.com/apache/arrow/blob/master/java/vector/src/main/java/org/apache/arrow/vector/ipc/message/MessageSerializer.java#L569

• https://github.com/apache/arrow/blob/master/java/vector/src/main/java/org/apache/arrow/vector/ipc/message/MessageSerializer.java#L290

  In C++, we have abstracted memory allocation out of the IPC read path so that zero-copy is possible. I suggest that a similar mechanism can be developed for Java to improve deserialization performance for in-memory messages. The new interface would return ArrowBuf when performing reads, which could be zero-copy when possible, but when not the current strategy of allocate-copy could be used

Reporter: Wes McKinney / @wesm

_{Note: This issue was originally created as ARROW-3192. Please see the migration documentation for further details.}

[asfimport]

Wes McKinney / @wesm:
cc @BryanCutler, in case this might impact Spark anywhere

[asfimport]

Bryan Cutler / @BryanCutler:
Thanks @wesm, yes I think these would affect Spark. I'll try to take a closer look at this when I can.