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

從 BufferAllocator.close() API 開始，追蹤資料物件仍在使用 allocator 時它如何處理已配置的記憶體。在確定實作與測試位置之前，釐清預期的擁有權與生命週期行為；當約定的 close 行為已針對仍在使用的物件實作並完成驗證時，即視為完成。

由索引模型根據 Issue 內容生成。