proposed changes for Neo4j 4.2 logging

[sarmbruster]

In the test class I'm using the LogManager being shaded into Neo4j instead of the regular one from Log4j2. Since we no longer depend on non-shaded log4j2 I've removed the dependency in pom.xml

For a unknown reason I wasn't able to read the config in json format using the shaded log manager. Therefore I'm providing a yaml variant of this.

Additionall I've added a sys variable to enable verbose log4j2 tracing.

WIth these changes the test passes.

[nioertel]

Thanks Stefan.

This workaround may be applicable in certain scenarios but it's not a general solution (specifically also not in my case). It doesn't work for the following scenarios:

• There is code that's independent from Neo4j and uses Log4j2 API (here we cannot switch from org.apache.logging.log4j.LogManager to org.neo4j.logging.shaded.log4j.LogManager)
• There is code using SLF4J API and we want to route it through Log4j2 using log4j-slf4j-impl (org.apache.logging.slf4j.Log4jLoggerFactory directly depends on org.apache.logging.log4j.*)

PS: I deleted the log4j2-test.yaml and it picks up the json file on my side.