Allow JansiLoader to print issues to java Logger instead of System.err

[blaghed]

In the JansiLoader.java class, exceptions are pushed directly to System.err.
E.g.:

System.err.printf(
        "Failed to load native library:%s. osinfo: %s%n",
        libPath.getName(), OSInfo.getNativeLibFolderPathForCurrentOS());

My original issue is the same as reported on #297 -- file access is fine, this library just doesn't work well with static native images using musl.
At the very least, I would like to redirect the error to an appropriate log file instead of just having it blasted out on the console like this:

Failed to load native library:jansi-2.4.1-ce6b715db40c9640-libjansi.so. osinfo: Linux/x86_64
java.lang.UnsatisfiedLinkError: Can't load library: /tmp/jansi-2.4.1-ce6b715db40c9640-libjansi.so

For reference, the exact same thing happens with JLine, but at least there they output to Logger already, so I would like to ask that this class does the same, please:
https://github.com/jline/jline3/blob/jline-3.30.4/native/src/main/java/org/jline/nativ/JLineNativeLoader.java#L411-L415

log(
        Level.WARNING,
        "Failed to load native library:" + libPath.getName() + ". osinfo: "
                + OSInfo.getNativeLibFolderPathForCurrentOS(),
        e);

(...)
    private static void log(Level level, String message, Throwable t) {
        if (logger.isLoggable(level)) {
            if (logger.isLoggable(Level.FINE)) {
                logger.log(level, message, t);
            } else {
                logger.log(level, message + " (caused by: " + t + ", enable debug logging for stacktrace)");
            }
        }
    }

[blaghed]

FYI, took the liberty of creating a suggestion PR for this.

[garretwilson]

Please use SLF4J instead of JUL. SLF4J has long been the de-facto standard Java facade, and it allows you to configure it to route to whichever logging subsystem you want, including JUL, Log4J, Logback, etc. A consuming application can simply add a dependency to automatically chose the SLF4J routing.

If the library uses JUL, then rerouting the logging becomes very programmatic, as JUL is very low-level. Not only does one need to add a bridge dependency to reroute JUL to SLF4J, extra code is required to remove the JUL loggers and replace them with the SLF4J routing. This would not be needed if the library used SLF4J from the beginning.

[blaghed]

I can't say I agree with that comment, but I also don't really care. If adding an additional library is what the repo owners want, then I can re-write the PR suggestion to fit that, just let me know.