SLF4J warnings in docker build/run

Describe the bug

When using the docker scripts to build and run unitycatalog, I get the same error messages as in #269:

SLF4J(W): No SLF4J providers were found.
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
2024-08-30T07:15:56.064512986Z main ERROR Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
2024-08-30T07:15:56.074533711Z main ERROR LogManager returned an instance of org.apache.logging.log4j.simple.SimpleLoggerContextFactory which doesnot implement org.apache.logging.log4j.core.impl.Log4jContextFactory. Unable to initialize Log4j.

To Reproduce

Steps to reproduce the behavior:

1. git clone https://github.com/unitycatalog/unitycatalog.git
2. cd unitycatalog
3. ./docker/bin/build-uc-server-docker
4. docker run $image_generated_above

Expected behavior

Logging to be functional

System [please complete the following information]:

• OS: Ubuntu 22.04 in WSL2 on Windows 11

Additional context

I'm trying in parallel to see what the difference is to the build process described in #269 but maybe someone has a better idea already.

Start with docker/bin/build-uc-server-docker and reproduce the warnings when running the generated image. Compare the Docker build and run process with the approach described in issue #269, then verify that the image starts with functional logging and without the reported SLF4J and Log4j warnings.