Factor out java.desktop and java.datatransfer module dependencies

Currently both jna-5.0.0.jar and jna-platform-5.0.0.jar depend on the java.desktop and java.datatransfer module:

$ jdeps -s jna-5.0.0.jar
jna-5.0.0.jar -> java.base
jna-5.0.0.jar -> java.desktop
jna-5.0.0.jar -> java.logging

$ jdeps -s jna-platform-5.0.0.jar
jna-platform-5.0.0.jar -> java.base
jna-platform-5.0.0.jar -> java.datatransfer
jna-platform-5.0.0.jar -> java.desktop
jna-platform-5.0.0.jar -> java.logging
jna-platform-5.0.0.jar -> not found

This is unfortunate as a lot of good usecases (the MariaDB JDBC driver for example) require JNA without needing anything from the desktop or AWT. This makes it much harder to generate compact JRE images for server-side applications as it forces one to pull in all the desktop-related stuff.

Consider splitting the jars in order to isolate the java.desktop and java.datatransfer related parts in their own module to enable server-side applications requiring JNA to run on much smaller JRE images.

Start by reviewing the module dependencies reported by jdeps for jna-5.0.0.jar and jna-platform-5.0.0.jar, then identify which parts require java.desktop and java.datatransfer. The work is complete when those dependencies are isolated so server-side JNA users can build smaller JRE images without desktop modules.