Update Apache Fuseki server dependency to permanently remove log4j security vulnerability

[mpsonntag]

The log4j version (2.14.1) used in the current build of the Apache Fuseki server contains a severe security vulnerability, see logging.apache.org for details.

Upgrade the Apache Fuseki server as soon as a fixed version (dependency Log4j >= 2.15.0) is released (4.3.0 still contains the vulnerable library). The used version can be checked in fuseki-server.jar:METAINF/DEPENDENCIES.

[mpsonntag]

New versions (4.3.1 and 4.3.2) of the Fuseki server have been released, using the 2.15.0 and 2.16.0 version of Log4j respectively, both plugging a security vulnerability each, see logging.apache.org for details. Since yet another vulnerability in Log4j has popped up that will only be addressed with Log4j version 2.17.0, the Fuseki server will not be updated until a version is released that contains Log4j >= 2.17.0 since the severe security vulnerability has been patched in the current running version.

[mpsonntag]

The Fuseki server 4.4.0 has completely changed the frontend, moving it from individual source files into the compiled source code. The current server setup needs to be rewritten and the binary custom compiled to continue using the custom odml-query frontend changes.
To not keep the log4j issues unaddressed in the meantime, the fuseki server version has been upgraded to 4.3.2 which contains log4j v2.16.0 fixing the two main security issues with PR #14.