[Java] Request for enhancements to BufferAllocator.close()

We are using Arrow in a production environment and running into some issues with memory allocation. Specifically, we would like to be able to call `BufferAllocator.close()` and have that clean up the allocated memory even if there are existing data objects using it, rather than the method throwing an exception upon seeing that the allocator is still in use. Are there any plans to add support for releasing memory on demand? 

**Reporter**: [Talia Trilling](https://issues.apache.org/jira/browse/ARROW-14328)

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

Comienza con la API BufferAllocator.close() y sigue cómo gestiona la memoria asignada cuando los objetos de datos todavía están usando el allocator. Aclara el comportamiento previsto de ownership y ciclo de vida antes de identificar las ubicaciones de implementación y de pruebas; se considera terminado cuando el comportamiento de cierre acordado está implementado y verificado para los objetos pendientes.

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