Add team_name tag to dag processor metrics for multi-team deployments

[ferruzzi]

Part 6 of 6, adding team_name to all metrics when available.

Follow-up to #68108
Can be reviewed/merged in parallel with #68367, #68589, #68593, and #68594

---

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

• Yes (please specify the tool below)

---

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

[ferruzzi]

Failing CI is legit, I'll fix it when I get a sec.

[o-nikolas]

I think this one is okay, since it only affects that multi_team=True path, so by default there will be no impact. But in the future we're probably going to want to optimize this. Some ideas that come to my head:

1. Memoizing the the DagBundleModel.get_team_name(...) call, or creating some
2. Create a bundle_name: team mapping/cache like we do in the scheduler
3. Could also read the bundle to team mapping from config, since it's specified in Airflow config, that would safe the DB round trip (but you'd probably want to still do one of the top two in addition to that).

[ferruzzi]

That's fair. I'll get this merged so we know it'll be in 3.3.0 and follow up immediately with a cached helper like I did with the scheduler. It should be up today; I'll tag you when it's ready.