Remove redundant logs from hive server from Azure CI 4th module

When there is an error or failure, we can see at the bottom there are some redundant logs from hive server, which is confusing.

 
{code:java}
2024-02-23T14:16:56.5032362Z ##[error]SLF4J: Class path contains multiple SLF4J bindings.
2024-02-23T14:16:56.5298013Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/slf4j/slf4j-reload4j/1.7.36/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5299627Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.17.2/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5300659Z ##[error]SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2024-02-23T14:16:56.5303968Z ##[error]ng is of type [org.slf4j.impl.Reload4jLoggerFactory]
2024-02-23T14:16:56.5307486Z ##[error]SLF4J: Class path contains multiple SLF4J bindings.
2024-02-23T14:16:56.5311372Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/slf4j/slf4j-reload4j/1.7.36/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5312540Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.17.2/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5314223Z ##[error]SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2024-02-23T14:16:56.5319464Z ##[error]SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory]
2024-02-23T14:16:56.5325886Z ##[error]log4j:WARN No appenders could be found for logger (org.apache.hudi.hadoop.fs.HadoopFSUtils).
2024-02-23T14:16:56.5328637Z ##[error]perly.
2024-02-23T14:16:56.5329457Z ##[error]log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
2024-02-23T14:16:56.5333098Z ##[error]SLF4J: Class path contains multiple SLF4J bindings.
2024-02-23T14:16:56.5334067Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/slf4j/slf4j-reload4j/1.7.36/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5335118Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.17.2/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5336283Z ##[error]SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2024-02-23T14:16:56.5337413Z ##[error]SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory]
2024-02-23T14:16:56.5338200Z ##[error]SLF4J: Class path contains multiple SLF4J bindings.
2024-02-23T14:16:56.5339865Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/slf4j/slf4j-reload4j/1.7.36/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5341013Z ##[error]SLF4J: Found binding in [jar:file:/root/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.17.2/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2024-02-23T14:16:56.5341919Z ##[error]SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2024-02-23T14:16:56.5342719Z ##[error]SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory]
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]r=2024-02-23
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
##[error]OK
{code}

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-7439
- Type: Bug

Start with the Azure CI configuration for the fourth module and trace how the Hive server process and its logging dependencies are launched. Reproduce a failing run and inspect the SLF4J and log4j output. Done means the redundant Hive server messages no longer appear as CI errors while the underlying failure remains visible.

Written by the indexing model from the issue text.