Provide a ByteBuffer based write path

Similar to the effort to use a ByteBuffer in the read path, we should provide a path to use a ByteBuffer in the write path.

The proposed idea is to provide an allocator in the writer that is passed down to CapacityByteArrayOutputStream and is used to allocate a ByteBuffer instead of the byte array that it currently uses.

I've attached a patch based on the 1.5 release that does that. There are two implementations of the allocator - one for Heap memory and one for Direct memory. In addition, the allocator interface allows for a 'release' method so that reference counted memory allocators like Netty's ByteBuf can be used to provide an allocator.

**Reporter**: [Parth Chandra](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=parthc) / @parthchandra
#### Related issues:
- [Move off of Parquet fork](https://issues.apache.org/jira/browse/DRILL-1410) (is depended upon by)

_{**Note**: *This issue was originally created as [PARQUET-78](https://issues.apache.org/jira/browse/PARQUET-78). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

Commencez par comparer le chemin de lecture existant basé sur ByteBuffer avec le writer et le CapacityByteArrayOutputStream mentionnés dans l’issue. Suivez la manière dont l’allocator proposé fournirait des buffers heap ou direct et dont leur libération serait gérée, puis vérifiez que le chemin d’écriture prend en charge les deux implémentations de l’allocator ainsi que la mémoire comptée par référence.

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