Revise integrated logging solutions

[GuusLieben]

Description

Provide a revised solution to providing loggers to components, without the need for a ApplicationLogger.

Current behavior

The current integrated logging solution, specifically the ApplicationLogger (which is partially implemented by the CallerLookupApplicationLogger, which in turn is extended by Slf4jApplicationLogger and LogbackApplicationLogger offers easy access to loggers anywhere you can access a ApplicationLogger. As ApplicationContext extends this interface, it is thus possible to use loggers anywhere you have a ApplicationContext. While this is great for internal development, where we often have direct access to a ApplicationContext, it is not optimal for third parties using the framework.

Use case

Making it easier to access loggers can motivate third parties to apply proper logging techniques in their applications. Additionally, it would be possible for us to better align the provision of logging to the rest of the framework.

Expected behavior

While a simple solution would be to offer only a configuration for logging (currently for Logback), which would allow users to obtain a logger through a LoggerFactory, that solution does not align with the framework's common approaches (though it should be noted that this approach is valid, and should remain supported).

A preferable way would be to provide default bindings for a application global logger, without the ApplicationLogger abstraction.

Additional context

No response

Related issues

No response

Possible implementations

No response