Run check-provider-yaml-valid when prek scripts or providers config change

[dabla]

Currently, selective checks skip check-provider-yaml-valid unless a provider.yaml, pyproject.toml, or provider Python file changed. This means that when only scripts/ci/prek/check_provider_yaml_files.py or providers/.pre-commit-config.yaml is modified, the check is silently skipped — so a bug introduced in the check script itself goes undetected in CI.

This was the root cause of the FileNotFoundError for providers/apache/provider.yaml reported after #70007 merged: the
_resolve_provider_yaml_files() function mapped any provider Python file to <pkg>/provider.yaml without guarding against non-provider-package paths like apache/, but check-provider-yaml-valid never ran in that PR's CI to catch it.

Changes

• Add providers/.pre-commit-config.yaml to
  ALL_PROVIDERS_DISTRIBUTION_CONFIG_FILES so changes to the providers
  prek configuration are treated like provider.yaml changes.
• Add PREK_FILES as an additional condition: when any prek script
  changes, check-provider-yaml-valid is no longer skipped.
• Add a test covering both trigger paths.
• Update dev/breeze/doc/ci/04_selective_checks.md to document the new
  rule.

Related

• Bug introduced by: #70007
• Static check fix: #70224

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

• [ x ] Yes (please specify the tool below)

Claude Sonnet 4.6 (GitHub Copilot CLI)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[github-actions]

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker ff0ac28 v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[Lee-W]

#70282