Add minute-level log retention for log groomer | issue #61814

[MiteshSahu]

Description

Add minute-level log retention support for log groomer sidecar containers to enable sub-day log rotation in remote logging scenarios (e.g., OpenTelemetry FileLog Receiver).

Changes:

• Add AIRFLOW__LOG_RETENTION_MINUTES environment variable (takes precedence over AIRFLOW__LOG_RETENTION_DAYS)
• Add Helm chart logGroomerSidecar.retentionMinutes configuration option for all deployment types (workers, scheduler, triggerer, dag-processor)
• Update log cleanup script to use find -mmin when minutes are configured, fallback to -mtime (days) otherwise
• Add unit and Helm integration tests for new functionality
• Backward compatible: defaults to days-based retention when minutes not specified

Type of change

• New feature
• Bug fix
• Documentation update
• Breaking change

Testing

• Added parameterized unit tests in airflow-core/tests/unit/charts/log_groomer.py
• Added Helm integration tests in helm-tests/tests/chart_utils/log_groomer.py
• Verified prek static code checks pass (RST, YAML, license headers)
• Local validation: Helm template rendering and cleanup script logic confirmed

Related Issue

Closes #61814

[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

[n-badtke-cg]

duplication with #61853

[potiuk]

@MiteshSahu 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: Airflow CTL tests / airflow-ctl:P3.10 tests. Run prek run --from-ref main locally to reproduce. See static checks docs.

Note: Your branch is 685 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

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.
• 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. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[n-badtke-cg]

This PR is obsolete now since PR #61855 got merged