[Java] Potentially inefficient variable-width vector reallocation

In several places in the Java codebase you can see this kind of pattern:
```java

while (vector.getDataBuffer().capacity() < toCapacity) {
vector.reallocDataBuffer();
}
```

In the event that a much larger capacity is requested, this will spuriously make several reallocations (doubling the capacity each time).

It would probably be more efficient to reallocate directly to satisfy the desired capacity.

Coincidentally, there's a `reallocDataBuffer` overload that seems to do just that.

**Reporter**: [Antoine Pitrou](https://issues.apache.org/jira/browse/ARROW-17919) / @pitrou

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

Comienza localizando los puntos de llamada de Java que iteran sobre vector.getDataBuffer().capacity() y llaman a reallocDataBuffer(); después, inspecciona la sobrecarga de reallocDataBuffer que acepta una capacidad deseada. Actualiza las rutas afectadas para que una capacidad mayor solicitada se satisfaga directamente y verifica que las pruebas de Java pertinentes cubran el comportamiento de realocación.

Escrito por el modelo de indexación a partir del texto del issue.