Triggerer warning about remote logging but not enabled

### Under which category would you file this issue? Airflow Core ### Apache Airflow version 3.2.2 ### What happened and how to reproduce it? We have just upgraded to Airflow 3.2.2. Since then, we have been seeing the below line in the triggerer logs (once per task instance, I believe): `[warning ] remote_log_handler_unavailable [airflow.logging.remote] loc=log.py:236 note='Remote log handler could not be loaded; logs will be available locally only.'` What's weird is that `AIRFLOW__LOGGING__REMOTE_LOGGING` should have the default value (False), so I am not sure why it's trying to use the remote log handler. ### What you think should happen instead? _No response_ ### Operating System Debian GNU/Linux 12 (bookworm) ### Deployment Other Docker-based deployment ### Apache Airflow Provider(s) _No response_ ### Versions of Apache Airflow Providers ``` apache-airflow-providers-common-compat | 1.15.0 apache-airflow-providers-common-io | 1.7.2 apache-airflow-providers-common-sql | 2.0.0 apache-airflow-providers-ftp | 3.15.0 apache-airflow-providers-git | 0.4.0 apache-airflow-providers-http | 6.0.3 apache-airflow-providers-imap | 3.11.3 apache-airflow-providers-keycloak | 0.7.3 apache-airflow-providers-postgres | 6.7.1 apache-airflow-providers-redis | 4.4.5 apache-airflow-providers-sftp | 5.8.1 apache-airflow-providers-smtp | 3.0.1 apache-airflow-providers-ssh | 5.0.2 apache-airflow-providers-standard | 1.13.1 ``` ### Official Helm Chart version Not Applicable ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _No response_ ### Anything else? The logging config for the triggerer: ``` [logging] base_log_folder = /opt/airflow/logs color_log_warning_keywords = warn,warning dag_processor_child_process_log_directory = /opt/airflow/logs/dag_processor json_logs = True ``` airflow info ``` Apache Airflow version …