[Improvement]: Application Logger log level setting

[IronSean]

Improvement description

After looking through the source code, and trying to use bin/console debug:config PimcoreApplicationLoggerBundle (only to see that "The extension with alias "pimcore_application_logger" does not have its getConfiguration() method setup. "), I can't see any easy way to configure a logging level for the application logger.

It would be useful to be able to set the minimum logging level so that anything calling the Application Logger will only log for Warning level or above. Especially for large datahub jobs this would allow to only log problematic rows instead of all rows. Dealing with multiple millions of rows of imports in datahub I've both created 300GB of application log tables and used up all available inodes on 500 GB data disk with the datahub file object files from the logging.

I've taken to manually truncating the log tables and purging the fileObjects because the lack of index on the level field in the application_logger table makes trying to preserve warning and error level logs too time consuming. Being able to filter so info level logs aren't made in the first place, but then be able to turn them on for additional logging when needed, would be very useful.

[github-actions]

Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.