Decide how to keep clean the terminal output when running on prod

[magicDGS]

Currently we have configured that the logs are output to the stderr instead of the stdout to be able to distinguish them from actual terminal output. This will enable that the stderr is output to a file on the running application, and then the stdout will be what will be shown in the terminal for the processing part.

We should consider some options to enable this processing to be useful, showing the progress, what was done, any possible failure, etc:

• Create a reporter interface that contains an implementation to both log and print to the stdout. The ammount of information might depend on some parameter that can be set into the CLI.
• Change the output for all the logs to a file directly instead of logging to stderr, and then control on the log that is output to stderr/stdout only the loggers that belong to our application (for example, INFO to stdout and WARN or higher to stderr).

[magicDGS]

Also, as we are refining/simplifying now the application configuration, we will remove the customization on the format for the logs in production, but this config can be useful if we go for the stdout logging idea to keep only the processing info:

quarkus:
  log:
    console:
      format: "[%-5p - %d{yyyy-MM-dd HH:mm:ss}] - %s%n"