ListVector#getBuffers returns buffers in the wrong order for usage of VectorLoader

Calling [getBuffers](https://github.com/apache/arrow/blob/06ca00c2daeeb0d6461e7b6bec51679c19b5b92b/java/vector/src/main/java/org/apache/arrow/vector/complex/ListVector.java#L652-L653) on a ListVector adds the offsetBuffers first and the validityBuffer second. When a ListVector is populated by [loadFieldBuffers](https://github.com/apache/arrow/blob/06ca00c2daeeb0d6461e7b6bec51679c19b5b92b/java/vector/src/main/java/org/apache/arrow/vector/complex/ListVector.java#L183-L189) (e.g. via a VectorLoader), the validityBuffer is read first and the offsetBuffer is read second. The resulting vector represents different data than the originating vector.

**Reporter**: [Paul Horn](https://issues.apache.org/jira/browse/ARROW-16377)

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

Commencez dans java/vector/src/main/java/org/apache/arrow/vector/complex/ListVector.java, en lisant getBuffers et loadFieldBuffers ensemble, puis suivez la façon dont VectorLoader consomme les buffers. Le travail est terminé lorsqu’un ListVector sérialisé par getBuffers et chargé via loadFieldBuffers représente les mêmes données, les buffers de validité et d’offsets étant gérés de manière cohérente.

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