Fix missing _team_name on DagRun before some listener calls

[kacpermuda]

In multi-team deployments the scheduler fires on_dag_run_running / success / failed listener hooks from several code paths. Before this change, DagRun._team_name was not guaranteed to be set when those hooks fired, so OpenLineage (and any other plugin reading _team_name) would miss the team on some events.

_team_name is a private attribute — it is not part of any public API and is not guaranteed to be present on every DagRun object a listener receives. Since the value is already cached in self._dag_id_to_team_name for metrics purposes, setting it consistently before each hook fires adds no cost. Listeners that wish to use it should treat it as best-effort and guard accordingly.

This PR ensures _team_name is stamped on every ORM DagRun object before notify_dagrun_state_changed() is called, covering all five listener code paths. The stamping is cheap: _get_team_names_for_dag_ids caches results in self._dag_id_to_team_name for the lifetime of a scheduler loop, so most calls are a dict read with no DB query. I've also added comments to the existing stamping paths, just to make sure it's clear why it's done before listener call.

---

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

• Yes — Claude Code (Sonnet 4.6)

Generated-by: Claude Code (Sonnet 4.6) following the guidelines

---

• 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.

[kacpermuda]

cc @ferruzzi , FYI as I see that you worked on adding this before

[uranusjr]

I would introduce a helper (say _stamp_team_names) to do the stamping instead of repeating the same logic multiple times. It would also help clean up the verbose comment added on every stamping block.

[kacpermuda]

I would introduce a helper (say _stamp_team_names) to do the stamping instead of repeating the same logic multiple times. It would also help clean up the verbose comment added on every stamping block.

@uranusjr Extracted the logic to a separate helper, ptal

[vatsrahul1001]

@kacpermuda can you resolve comments?

[kacpermuda]

@vatsrahul1001 addressed all the comments

[vatsrahul1001]

LGTM!, can be merged after code owners review

[jason810496]

Thanks, LGTM overall.

[vatsrahul1001]

Moving to 3.3.2 as this is still pending code owner review and do not want to rush on merging this as it not critical

[github-actions]

Backport successfully created: v3-3-test

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