[Java] Netty memory release

### Describe the bug, including details regarding any error messages, version, and platform.

Since when we use netty as my memory allocator manager, I found that direct memory is not released after vector is closed.
```
Field field = new Field("test", FieldType.nullable(new ArrowType.Utf8()), null);
RootAllocator allocator = new RootAllocator(Long.MAX_VALUE);
FieldVector vector = field.createVector(allocator);
for (int i = 0; i < 100000; i++){
((VarCharVector)vector).setSafe(i, "test".getBytes(StandardCharsets.UTF_8));
}

System.out.println("before close memory: " + usedDirectMemory() + " bytes"); //before close memory: 4194304 bytes
vector.close();
allocator.close();
System.out.println("after closed memory: " + usedDirectMemory() + " bytes"); //after closed memory: 4194304 bytes
```
I can address the problem that if the inner allocator `PooledByteBufAllocator` won't free the memory chunk , I am not sure if this is expected.

### Component(s)

Java

從使用 RootAllocator、VarCharVector 和 PooledByteBufAllocator 的 Java 重現開始，然後追蹤 allocator 的關閉行為以及 Netty 對直接記憶體的處理。確認剩餘的 4194304 位元組究竟是實際的洩漏，還是預期的池化行為，並記錄或測試由此得到的預期行為。

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