Use SLF4J, avoid interfering with application logging

[ebaron]

When testing with EAP, we found a conflict with our JUL logging and EAP's logging that prevented it from starting. This PR ports over the logging setup from https://github.com/cryostatio/cryostat-agent that avoids this problem using an SLF4J configuration that avoids conflicts with the host application's logging.

This implementation was originally done by @andrewazores

[andrewazores]

Looks like it matches the cryostat-agent workaround.

[ebaron]

We're seeing similar errors with EAP in Cryostat on OpenShift, converting this to a draft until we've figured it out.

[ehsavoie]

You should use MODULE_OPTS instead of JAVA_OPTS to pass your agent thus you would avoid that logmanager issue

[ebaron]

We're seeing similar errors with EAP in Cryostat on OpenShift, converting this to a draft until we've figured it out.

This turned out to be due to a separate issue where the same crash occurs by enabling remote JMX (with or without an agent): https://access.redhat.com/solutions/312453

You should use MODULE_OPTS instead of JAVA_OPTS to pass your agent thus you would avoid that logmanager issue

I tried this and it works well for EAP 7.4.0+, but this could still help to simplify installing our agent with older versions of EAP.

[kittylyst]

LGTM.