Fixes #50963

This PR separates the control of log format (console vs JSON) from log styling (colors and rich traces) in the Task SDK logging configuration. Previously, the single enable_pretty_log boolean controlled both aspects, making it impossible to have console logs without colors and rich traces.

Problem

• Single enable_pretty_log boolean controlled BOTH format (console vs JSON) AND styling (colors + rich traces)
• No way to get console logger without colors and rich traces
• Celery workers showed color escape sequences as raw text in log ingestion solutions like Splunk

Solution

• Separated enable_pretty_log (format) from enable_colors (styling)
• enable_pretty_log=True + enable_colors=False = plain text console logger (no colors, no rich traces)
• Respects existing colored_console_log configuration parameter
• Celery workers automatically respect the configuration without code changes
• Change is backwards compatible since:
  • configure_logging() - uses default enable_colors=None → reads config
  • logging_processors(enable_pretty_log=True) - uses default enable_colors=True

New Behavior Matrix:

Testing

All new & existing tests are passing, as well as the pre-commit checks. I wrote some simple unit tests in the test SDK,

• test_logging_processors_with_colors(): Verifies colored console renderer
• test_logging_processors_without_colors(): Verifies non-colored console renderer
• test_logging_processors_json_format(): Verifies JSON renderer unchanged
• test_configure_logging_respects_colored_console_log_config(): Tests configuration reading
• test_configure_logging_explicit_enable_colors(): Tests explicit parameter override
• test_configure_logging_no_airflow_config(): Tests fallback behavior

Since I am new to the project, I also wrote a short testing script (attached as a .txt) and ran it in my local Breeze environment, here were the results:

demo_test.txt