Fix: add RUN, HITL_DETAIL, TASK_INSTANCE entities to /dags endpoint as it returns nested entities in response

[sjyangkevin]

The /dags endpoint returns nested entities include RUN, and HITLDetail includes TaskInstanceResponse. Add related access entity to govern the endpoint.

class DAGWithLatestDagRunsResponse(DAGResponse):
    """DAG with latest dag runs response serializer."""

    asset_expression: dict | None
    latest_dag_runs: list[DAGRunLightResponse]
    pending_actions: list[HITLDetail]
    is_favorite: bool

---

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

• Yes (please specify the tool below)

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.

[pierrejeambrun]

Looking good. We might need a significant newsfragment just to mention this. Just a disclaimer for people to double check their users permissions check or they might have unintended forbidden errors.

[sjyangkevin]

Looking good. We might need a significant newsfragment just to mention this. Just a disclaimer for people to double check their users permissions check or they might have unintended forbidden errors.

Thanks! I will look into how to add a newsfragment for this change.