Execution API: Resolve retry callback team via TI history

[GayathriSrividya]

closes #67923

Summary

This PR fixes retry callback team-name resolution in the execution API.

Root cause

Team lookup could miss in retry/history-backed paths when only active task-instance context was considered, causing downstream failures (500 / SQLAlchemy argument errors).

Changes

• Update execution API team lookup to resolve from both:
  • task_instance
  • task_instance_history
• Keep behavior unchanged when multi-team is disabled.

Tests

Added coverage in airflow-core/tests/unit/api_fastapi/execution_api/test_security.py for:

• sync helper behavior with multi-team on/off
• SQL statement includes both TI and TI history sources (UNION ALL)

Local validation

• Ruff format/check passed on modified files.
• uv run --project airflow-core pytest airflow-core/tests/unit/api_fastapi/execution_api/test_security.py -xvs passed.

Scope

This change is intentionally scoped to retry callback team-name resolution only.

[potiuk]

@GayathriSrividya — I've removed the ready for maintainer review label because the next step here is yours: this branch now has merge conflicts with main. It'll go back into the maintainer queue automatically once you rebase onto the latest main and push — no need to re-add the label by hand. There's no rush.

_{Automated triage note drafted by an AI-assisted tool — may get things wrong; a real Apache Airflow maintainer takes the next look once it's green. (why automated)}

---

Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting

[GayathriSrividya]

@GayathriSrividya — I've removed the ready for maintainer review label because the next step here is yours: this branch now has merge conflicts with main. It'll go back into the maintainer queue automatically once you rebase onto the latest main and push — no need to re-add the label by hand. There's no rush.

Automated triage note drafted by an AI-assisted tool — may get things wrong; a real Apache Airflow maintainer takes the next look once it's green. (why automated)

Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting

I’ve rebased this onto the latest main commit to branch. It should be back in sync now.