feat(db/rocksdb): improve resource management with try-with-resources

[halibobo1205]

What does this PR do?

This PR improves native memory management in RocksDB operations by properly closing WriteOptions and ReadOptions objects using try-with-resources statements.

Why are these changes required?

RocksDB Java objects like WriteOptions, ReadOptions, Options, and RocksIterator wrap native C++ objects and hold off-heap memory that is not managed by the JVM garbage collector. According to the RocksJava Basics - Memory Management documentation:

"Many of the Java Objects used in RocksJava will free their associated C++ objects when they are garbage collected via their finalize() method; however, this may take some time to occur. To speed this up it is best to explicitly call the close() method (or use try-with-resources) of any objects which implement java.lang.AutoCloseable."

This PR has been tested by:

• Unit Tests
• Manual Testing

Follow up

Extra details

1. Test

Code Version	Architecture	JDK	GC	DB	Memory Used
Leak	arm64	8	G1GC	rocksDB	Stable leak
Fixed	arm64	8	G1GC	rocksDB	No leak, stable 2G
Leak	x86	8	G1GC	rocksDB	No leak, stable 3G
Fixed	x86	8	G1GC	rocksDB	No leak, stable 3G
Leak	arm64	17	G1GC	rocksDB	Stable leak
Fixed	arm64	17	G1GC	rocksDB	No leak, stable 3G
Leak	x86	17	G1GC	rocksDB	No leak, stable 3G
Fixed	x86	17	G1GC	rocksDB	No leak, stable 3G
Leak	arm64	17	ZGC	rocksDB	Stable leak
Fixed	arm64	17	ZGC	rocksDB	No leak, stable 830M
Leak	x86	17	ZGC	rocksDB	No leak, stable 900M
Fixed	x86	17	ZGC	rocksDB	No leak, stable 920M

Summary

• Memory leak issue is specific to arm64 architecture: All unfixed versions on arm64 exhibit stable memory leaks, regardless of JDK version (8 or 17) or GC type (G1GC or ZGC)
• x86 architecture shows no memory leaks: Both unfixed and fixed versions on x86 maintain stable memory usage without leaks
• The fix resolves arm64 memory leaks: After applying the fix, arm64 systems stabilize at consistent memory levels
• ZGC shows better memory efficiency: On both architectures with JDK 17, ZGC uses significantly less memory (~830-920M) compared to G1GC (~3G)
• The issue appears to be an arm64-specific bug: The problem is isolated to the arm64 platform and is successfully resolved by the code fix

2. reference linking

• RocksJava Memory Management
• Automatic Resource Management for the Java API

[waynercheung]

LGTM