[Bug]: lack of logging control by configuration & integration to the observability ecosystem

### Apache Hop version?

SNAPSHOT

### Java version?

21

### Operating system

Linux

### What happened?

Details are in the description of the PR https://github.com/apache/hop/pull/8320

High level it should be trivial to switch the output format to some structured logging, local/remote channels (kafka appender for example) and get observability for free without coding (opentelemetry commong log integration at least doesn't sound a crazy assumption).

Literally the expectation is to use a standard logger - JUL, Log4j2, logback or anything "known".

Side note: since log4j2 is already in the stack with slf4j abstraction it sounds the default good choice for that feature.

### Issue Priority

Priority: 2

### Issue Component

Component: Hop Run

Start with the description of PR #8320 and the Apache Hop Run component, then review how logging is currently configured for the Java application. Done means providing configurable standard logging with structured output and support for local or remote observability integrations, as described in the issue.

Written by the indexing model from the issue text.