Add team_name tags to Edge worker metrics

[shivaam]

Add the team_name tag to Edge worker metrics for multi-team deployments.

This follows the same pattern as the merged core metric PRs and #69005:

• use prune_dict so global/no-team workers keep the existing tag set
• keep legacy metric names unchanged
• cover both team-scoped and no-team paths in unit tests

This PR covers the Edge worker metrics from #68996:

• edge_worker.heartbeat_count
• edge_worker.status
• edge_worker.connected
• edge_worker.maintenance
• edge_worker.jobs_active
• edge_worker.concurrency
• edge_worker.free_concurrency
• edge_worker.num_queues
• numeric edge_worker.<sysinfo_key> gauges
• edge_worker.ti.start
• edge_worker.ti.finish

It also passes the worker team_name through the Edge executor orphan/liveness paths so worker reset and orphaned task-finish metrics keep the correct team attribution.

Notes:

• Add team_name tag to Edge executor sync metric #69005 covers edge_executor.sync.duration separately.
• ECS/Amazon executor metrics are kept out of this PR.
• Bring back edge worker metric compatibility with Airflow 3.2 #67328 also touches Edge worker metric compatibility; this branch was rebased after confirming Bring back edge worker metric compatibility with Airflow 3.2 #67328 is still open.

Tests:

• uv run ruff format --check providers/edge3/src/airflow/providers/edge3/executors/edge_executor.py providers/edge3/src/airflow/providers/edge3/models/edge_worker.py providers/edge3/src/airflow/providers/edge3/worker_api/routes/jobs.py providers/edge3/src/airflow/providers/edge3/worker_api/routes/worker.py providers/edge3/tests/unit/edge3/executors/test_edge_executor.py providers/edge3/tests/unit/edge3/worker_api/routes/test_jobs.py providers/edge3/tests/unit/edge3/worker_api/routes/test_worker.py
• uv run ruff check providers/edge3/src/airflow/providers/edge3/executors/edge_executor.py providers/edge3/src/airflow/providers/edge3/models/edge_worker.py providers/edge3/src/airflow/providers/edge3/worker_api/routes/jobs.py providers/edge3/src/airflow/providers/edge3/worker_api/routes/worker.py providers/edge3/tests/unit/edge3/executors/test_edge_executor.py providers/edge3/tests/unit/edge3/worker_api/routes/test_jobs.py providers/edge3/tests/unit/edge3/worker_api/routes/test_worker.py
• git diff --check
• breeze run pytest providers/edge3/tests/unit/edge3/executors/test_edge_executor.py providers/edge3/tests/unit/edge3/worker_api/routes/test_jobs.py providers/edge3/tests/unit/edge3/worker_api/routes/test_worker.py -q
• uvx prek run --from-ref upstream/main --stage pre-commit
• breeze ci selective-check --commit-ref HEAD

Related: #68996

---

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

• Yes - OpenAI Codex

Generated-by: OpenAI Codex following the guidelines

---

Drafted-by: OpenAI Codex (no human review before posting)

[SameerMesiah97]

Looks good. Could not find any issues.

[shivaam]

@ferruzzi This Pr is waiting for your review not sure if you got a notification.

[ferruzzi]

LGTM and follows the patterns established int he other related PRs. Wouldn't mind @jscheffl having eyes on it, and that (potential?) bug can definitely be handled in its own PR. Thanks.