4.x: Use System.Logger instead of JUL where applicable

[tomas-langer]

Revisit all usages of Java Util Logging (JUL) and replace relevant cases with System.Logger, so we can remove the dependency on java.logging from most of our modules.

The dependency is expected in:

• helidon-logging-jul - the integration with JUL
• temporary as a workaround for shutdown hook (I think in webserver), unless already abstracted (or abstract it into our logging implementations)
• examples and test scopes (to correctly log in these cases)

[jbescos]

Some modules contains public methods with dependencies to JUL:

helidon/common/reactive/src/main/java/io/helidon/common/reactive/Single.java

Line 576 in e0a91cb

default Single<T> log(Level level) {

helidon/webserver/access-log/src/main/java/io/helidon/webserver/accesslog/AccessLogHandler.java

Line 56 in fddb60f

public synchronized void setFormatter(Formatter newFormatter) throws SecurityException {

[jbescos]

Merged