libjna-jni uses the wrong path on aarch64

[Reinhard Pointner]

libjna-jni uses the wrong path on aarch64

The custom patch works on amd64 but not aarch64 because the will try to load from /usr/lib/arm-linux-gnueabi/jni/libjnidispatch.system.so on aarch64 (and also armv7, armhf, etc) which does not exist:
https://salsa.debian.org/java-team/libjna-java/-/blob/master/debian/patches/04-load-native-code-from-fs.patch

The package installs the library to /usr/lib/aarch64-linux-gnu/jni/libjnidispatch.system.so however:
https://packages.ubuntu.com/jammy/arm64/libjna-jni/filelist

Additionally, DO NOT IGNORE System Properties via a custom patch without System.err logging. I've tried debugging the problem based on the official JNA source and thought I was losing my mind when the jna.boot.library.path jna.boot.library.name System Properties didn't work, until I found out that the deb package patches them out for no apparent reason:
https://salsa.debian.org/java-team/libjna-java/-/blob/master/debian/patches/14-rename-native-library.patch#L11

Note that these system properties are not set by default. Why do you patch them out? Presumably, there was a reason, but I'd argue not doing that, because you don't wanna take away the ability to use them and fix things if needed. If those properties are set, then users / developers have set them for a reason, and should not be ignored, unexpectedly ignored no less.