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

Comece pela API BufferAllocator.close() e rastreie como ela lida com a memória alocada quando os objetos de dados ainda estão usando o allocator. Esclareça o comportamento pretendido de ownership e ciclo de vida antes de identificar os locais de implementação e de teste; considera-se concluído quando o comportamento de fechamento acordado estiver implementado e verificado para os objetos pendentes.

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