fix: forward task logs to stdout in LocalExecutor

[taranlu-houzz]

LocalExecutor's _execute_work() calls supervise() without passing
subprocess_logs_to_stdout=True, so task logs are only written to log
files and never reach the container's stdout. This breaks log collection
in deployments that rely on container stdout for log aggregation.

The containerized executor (execute_workload.py) already passes this
flag (added in #47731), but LocalExecutor was not updated.

closes: #54501
related: #49863

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Code (Anthropic)

Generated-by: Claude Code following the guidelines

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[potiuk]

@taranlu-houzz This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Other failing CI checks: Failing: Postgres tests: core / DB-core:Postgres:14:3.10:Core...Serialization, MySQL tests: core / DB-core:MySQL:8.0:3.10:Core...Serialization, Sqlite tests: core / DB-core:Sqlite:3.10:Core...Serialization, Low dep tests:core / All-core:LowestDeps:14:3.10:Core...Serialization. Run prek run --from-ref main locally to reproduce. See static checks docs.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

[taranlu-houzz]

The CI failures are all from test_execution_api_server_url_config (5 parametrized variants × 4 backend jobs = 20 failures) — the test mocks supervise() and asserts exact kwargs, so the new subprocess_logs_to_stdout=True parameter caused the mismatch.

Pushed a fix that updates the test assertion to expect the new parameter.

Edit: Claude sent this message. Still trying to figure out the best way to be transparent about working via an agent.

[eladkal]

Closing in favor of #64067