Expose db memory address and path to libduckdb_java.so V2

[Jens-H]

This PR replaces #87!

Same idea, but:

• using Java long instead of String to hold the memory address
• based on top of main HEAD

I read that DuckDB uses pointer swizzling, which should break before there is problem with the uintptr_t -> jlong cast. This means it should be OK to use it on all supported platforms.

[Jens-H]

I ran make format and committed some unrelated files and lines with dc0833a ... seems like without much success.

[Jens-H]

To add a rational for this change:
Since Java 22 the JEP 454 "Foreign Function & Memory API" left the preview status (https://openjdk.org/jeps/454) and is now the second official way to interact with native code.
This would open the option to use the faster C API (like columnar access) instead of the traditional JDBC methods. As JDBC is everywhere it should be possible to have both. Unfortunately the Duckdb database pointer is not accessible outside JNI. With the new method it is possible to rebuild the pointer when needed.

@Mause You reviewed the old PR, so maybe you can have a look.

[staticlibs]

Closing this as outdated. If this functionality is still required - this can be revisited.