Add team_name tag to Edge executor sync metric

[shivaam]

Add the team_name tag to the Edge executor sync duration metric for multi-team deployments.

This follows the same pattern as #68593 for executor metrics:

• use self.team_name as the metric tag source
• wrap tags with prune_dict so global/no-team executors keep the existing empty tag set
• keep the change scoped to the Edge executor metric only

This PR covers the edge_executor.sync.duration item from #68996. Edge worker metrics and ECS executor metrics are being kept in separate PRs.

Tests:

• uv run ruff format --check providers/edge3/src/airflow/providers/edge3/executors/edge_executor.py providers/edge3/tests/unit/edge3/executors/test_edge_executor.py
• uv run ruff check providers/edge3/src/airflow/providers/edge3/executors/edge_executor.py providers/edge3/tests/unit/edge3/executors/test_edge_executor.py
• git diff --check
• uv run pytest providers/edge3/tests/unit/edge3/executors/test_edge_executor.py -q
• breeze run pytest providers/edge3/tests/unit/edge3/executors/test_edge_executor.py -q
• uvx prek run --from-ref upstream/main --stage pre-commit

Results:

• ruff format/check passed
• diff check clean
• 20 passed, 1 warning
• pre-commit stage passed

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]

I have left some comments.

[shivaam]

Thanks @ferruzzi @SameerMesiah97 .

I updated the PR to match the existing Edge executor multi-team test pattern:

• added the AIRFLOW_V_3_2_PLUS guard for the EdgeExecutor(team_name=...) metric test
• parameterized the team/no-team assertions for the edge_executor.sync.duration metric tags
• kept prune_dict({"team_name": self.team_name}) so the no-team path continues to emit tags={} rather than team_name=None

[ferruzzi]

LGTM, thanks for taking this on.