Enable warning/error logs from libraries in tests

[findepi]

Warning and errors are rarely seen by engineers, but still it's better not to hide them, they may (now or in the future) contain some actionable information. When a library over-verbosely logs some warnings/errors, let's suppress these selectively.

Follows #19676

[findepi]

they may (now or in the future) contain some actionable information

I can't say that for sure for libraries we currently use in this project, but that's certainly my past experience.
Sometimes people use warnings in a manner similar to @Deprecated -- deprecation is suitable for staticaly compiled API elements, while warnings are used for things detected at runtime (like Trino's warning when ORDER BY gets ignored).

[martint]

Libraries should not be reporting problems via logging. If there’s an actionable error, they should fail with an exception.

These logs were turned off intentionally, precisely because they were generating noise in the CI logs that’s not actionable and just makes it harder to spot real problems such as test failures.

[findepi]

Libraries should not be reporting problems via logging. If there’s an actionable error, they should fail with an exception.

I tend to agree. But I do not get to choose what libraries do and I have been burned in the past by ignoring warnings from a library. This was so important that I even had a test framework to watch out for new warning/errors and it turned helpful in future situations.

Agreeing that we may need to suppress certain overly verbose loggers. For example Iceberg library is a known offender and logs A LOT at INFO level. So if they also log a lot at warn/error level then either we help them fix this, or suppress such a misbehaving library.

[losipiuk]

These logs were turned off intentionally, precisely because they were generating noise in the CI logs that’s not actionable and just makes it harder to spot real problems such as test failures.

@martint can you comment on the intention of turning off WARN/ERROR? I get why we do not want to have flooding of INFO logs from external libs but seeing errors in logs can point us to problems in our code. Even if not in an optimal way - it is good nonetheless.

I think this change is good and should have not been reverted.

[findepi]

Example useful warning logged by Iceberg library

WARN	Finalizer	org.apache.iceberg.aws.s3.S3FileIO	Unclosed S3FileIO instance created by:
	org.apache.iceberg.aws.s3.S3FileIO.<init>(S3FileIO.java:120)
	org.apache.iceberg.aws.s3.S3FileIO.<init>(S3FileIO.java:106)
        <caller>

i noticed this in some other application using Iceberg library. Wonder whether something like this gets logged when Trino uses Iceberg library.