[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.*}

Comece localizando os pontos de chamada Java que fazem loop sobre vector.getDataBuffer().capacity() e chamam reallocDataBuffer(); em seguida, inspecione a sobrecarga de reallocDataBuffer que aceita uma capacidade desejada. Atualize os caminhos afetados para que uma capacidade maior solicitada seja atendida diretamente e verifique se os testes Java relevantes cobrem o comportamento de realocação.

Escrita pelo modelo de indexação a partir do texto da issue.