Enable Log Aggregation for Trino

[maltesander]

See stackabletech/hbase-operator#291 and stackabletech/docker-images#283 for reference.

This is part of stackabletech/issues#288

TODO

• Switch to vector base image docker-images#320 -> obsolete, only new images must be build
• [Merged by Bors] - Add airlift log parsing for vector operator-rs#553
• [Merged by Bors] - Update operator rs and stackable versions #378
• [Merged by Bors] - Fragment trino config #379
• [Merged by Bors] - Enable logging #380

[maltesander]

In terms of Research (thanks to @lfrancke). Just to collect the results.

We managed to get logback working. This required adding and removing some jars from our docker image (using Trino v403):

### Log Testing
RUN curl -L https://repo1.maven.org/maven2/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar -o /stackable/trino-server/lib/jul-to-slf4j-1.7.36.jar && chmod -x /stackable/trino-server/lib/jul-to-slf4j-1.7.36.jar && \
    curl -L https://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.2.11/logback-classic-1.2.11.jar -o /stackable/trino-server/lib/logback-classic-1.2.11.jar && chmod -x /stackable/trino-server/lib/logback-classic-1.2.11.jar

RUN rm /stackable/trino-server/lib/slf4j-jdk14-1.7.36.jar && \
    rm /stackable/trino-server/lib/log4j-api-2.17.1.jar
### End test

Additional extending the jvm.config with:

-Djava.util.logging.config.file=/stackable/logging.properties
-Dlogback.configurationFile=/stackable/trino-server/lib/logback.xml

where the logging.properties and logback.xml were just hardcoded in the operator for testing.
The logging.properties:

handlers=org.slf4j.bridge.SLF4JBridgeHandler

and logback.xml:

<configuration>
  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
      <pattern>[LOGBACK START] timestamp: %d{yyyy-MM-dd HH:mm:ss.SSS}, thread: %thread, level: %-5level, logger: %logger{36}, message: %msg%n [LOGBACK END]</pattern>
    </encoder>
  </appender>
  <root level="info">
    <appender-ref ref="STDOUT" />
  </root>
</configuration>

This resulted in the logging messages being nested (prefixed with the StaticLoggingFormat):

2023-02-07T15:51:31.059Z	INFO	main	stdout	[LOGBACK START] timestamp: 2023-02-07 15:51:31.058, thread: main, level: INFO , logger: o.e.jetty.util.ssl.SslContextFactory, message: x509=X509@41271320(1,h=[simple-trino-coordinator-default.default.svc.cluster.local, simple-trino-coordinator-default-0.simple-trino-coordinator-default.default.svc.cluster.local, kind-worker, generated certificate for pod],a=[/172.18.0.4],w=[]) for Server@1de398c3[provider=null,keyStore=null,trustStore=null]
 [LOGBACK END]

This is way too hacky and requires changes upstream. For now we decided to use JSON logging for the server logs and pick up the bootstrap logs from the console.