Memory leaks in RocksDBDAO after rocksdbjni upgraded to 7

As stated in the following links

[Native memory leak through JNI after upgrading to 7.0.4|https://github.com/facebook/rocksdb/issues/9962]

[AbstractNativeReference.java|https://github.com/facebook/rocksdb/blob/v7.5.3/java/src/main/java/org/rocksdb/AbstractNativeReference.java]

After removed finalize() in RocksDB 7,it is required that users call {{close}} on RocksJava objects or use {{try-with-resource.}}

I found several rocksdb objects in RocksDBDAO that were not released properly, such as {{DBOptions}},{{ColumnFamilyOptions}},{{WriteOptions}} and {{RocksIterator}}.

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-7519
- Type: Bug

Start by locating RocksDBDAO and reviewing how its DBOptions, ColumnFamilyOptions, WriteOptions, and RocksIterator objects are created and released. Read the linked RocksDB 7 AbstractNativeReference guidance and issue 9962 first. Done means every listed native resource has an appropriate close lifecycle and the memory leak no longer occurs.

Written by the indexing model from the issue text.