DATAGO-73953: use slf4j instead of apache commons logging

[Nephery]

Use SLF4J instead of Apache Commons Logging.

Although the Spring team themselves uses LogAccessor (a wrapper around Apache Commons Logging) throughout the Spring codebase, we should be fine to use SLF4J since the Spring Logging starters allcome with the slfj4j-api dependency out-of-the-box:

• spring-boot-starter-logging
• spring-boot-starter-log4j2

[mgevantmakher]

this not going to log as expected: e not logged

/**
 * Log a message at the WARN level according to the specified format
 * and arguments.
 * 
 * <p>This form avoids superfluous object creation when the logger
 * is disabled for the WARN level. 
 *
 * @param format the format string
 * @param arg1   the first argument
 * @param arg2   the second argument
 */
public void warn(String format, Object arg1, Object arg2);

[Nephery]

You can use parameterized logging with a throwable as the last parameter. See https://www.slf4j.org/faq.html#paramException (Spring Boot 3.3.3 uses SLF4J 2.0.16).

For example, when I do:

LOGGER.warn("foo {}", "bar", new RuntimeException("test error", new RuntimeException("cause")));

I get the output:

2024-08-28T14:34:34.396-04:00  WARN   --- [           main] c.s.s.c.s.b.util.XMLMessageMapperTest    : foo bar

java.lang.RuntimeException: test error
Caused by: java.lang.RuntimeException: cause

[mgevantmakher]

org.slf4j . Logger are bit tricky and may not work as expected
warn(String format, Object arg1, Object arg2);
warn(String msg, Throwable t);
public void warn(String format, Object... arguments);