SuppressLoggerDeprecationFilter

Suppresses Play's startup warning: "Logger configuration in conf files is deprecated and has no effect. Use a logback configuration file instead."

Play emits this (in GuiceApplicationBuilder) whenever it finds log level values under the logger config path, on the assumption that nothing consumes them. On MDTP that assumption is false: LoggerModule reads those same logger.* entries at startup and applies them via Logback's setLevel, so config-driven log levels DO take effect.

This must be a Logback TurboFilter rather than logic in LoggerModule, because the warning is emitted during logger-factory configuration — before module bindings run — so by the time LoggerModule executes the message has already been logged. A TurboFilter is loaded with the Logback config (before the warning fires) and is consulted for every logging event, so it can drop this specific message at source.