[Java] Experiment with performance difference of avoiding the use of Avro Decoder

It has been posited that the Decoder object (and on-heap work in general) is potentially slow for decoding.

The scope of this Jira is to add a new method that instead of consuming from Decoder, consumes directly from a ByteBuffer.  In order to this we there needs to be utility classes for zig-zag decoding (one might existing in avro) from a ByteBuffer.

This is esentially rewriting logic in the decoder to work directly against a bytebuffer and then measure if there is a meaningful performance impact.

**Reporter**: [Micah Kornfield](https://issues.apache.org/jira/browse/ARROW-6593) / @emkornfield
#### Related issues:
- [[Java] Add support for skipping decoding of columns/field in Avro converter](https://github.com/apache/arrow/issues/22949) (is a clone of)

_{**Note**: *This issue was originally created as [ARROW-6593](https://issues.apache.org/jira/browse/ARROW-6593). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

Commencez par localiser le code de conversion Java Avro qui consomme Decoder et examinez les utilitaires Avro existants de décodage zig-zag. Le travail est terminé lorsque le décodage basé sur ByteBuffer et les utilitaires associés sont implémentés, et que les mesures montrent si le fait d’éviter Decoder et le travail sur le tas apporte un impact significatif sur les performances.

Rédigé par le modèle d'indexation à partir du texte de l'issue.