This pull request aims to fix some cases in LMDBJava where theBufferProxy'sout method resulting buffer is ignored, especially inDbi.

I've discovered this issue while attempting to write a new implementation ofBufferProxy to use Java 22's Function Foreign Memory API in preparation of Java 25's depreciation of various methods inUnsafe invalidating most fastBufferProxy implementations. The implementation failed to pass some tests since in theout method I returned a newByteBuffer (taking advantage ofMemorySegment.ofAddress().asByteBuffer()).

After further investigation, I've found thatByteArrayProxy also relies on returning a different "buffer" from the one that's given as an argument, for which I've added new tests that reproduce the behavior ofDbiTest.customComparator andDbiTest.dbiWithComparatorThreadSafety using byte arrays instead.ByteArrayProxy led me to think that returning a different buffer inout is an allowed and intended behavior.

This fix is important for users ofByteArrayProxy and allows for a stop-gap external implementation ofBufferProxy using the FFM API to allow users to upgrade to Java 25 when the time comes until a proper resolution to#42 comes around.