### Apache Airflow version

2.5.2

### What happened

when trying to delete a dag run with many tasks (>1000) the operation times out and the dag run is not deleted. 

### What you think should happen instead

_No response_

### How to reproduce

attempt to delete a dag run that contains >1000 tasks (in my case 10k) using the dagrun/list/ page results in a timeout:
![image](https://user-images.githubusercontent.com/7373236/226325567-5a87efa1-4744-417e-9995-b97dd1791401.png)


code for dag (however it fails on any dag with > 1000 tasks):
```
import json

from airflow.providers.cncf.kubernetes.operators.kubernetes_pod import KubernetesPodOperator
from datetime import datetime, timedelta
from airflow.decorators import dag, task

default_args = {
    'owner': 'airflow',
    'depends_on_past': False,
    'retries': 0,
    'retry_delay': timedelta(minutes=1),
    'start_date': datetime(2023, 2, 26),
    'is_delete_operator_pod': True,
    'get_logs': True
}


@dag('system_test', schedule=None, default_args=default_args, catchup=False, tags=['maintenance'])
def run_test_airflow():
    stress_image = 'dockerhub.prod.evogene.host/progrium/stress'  

    @task
    def create_cmds():
        commands = []
        for i in range(10000):
            commands.append(["stress --cpu 4 --io 1 --vm 2 --vm-bytes 6000M --timeout 60s"])
        return commands

    KubernetesPodOperator.partial(
        image=stress_image ,
        task_id=f'test_airflow',
        name=f'test_airflow',
        cmds=["/bin/sh", "-c"],
        log_events_on_failure=True,
        pod_template_file=f'/opt/airflow/dags/repo/templates/cpb_cpu_4_mem_16'
    ).expand(arguments=create_cmds())


run_test_airflow()

```

### Operating System

kubernetes deployment

### Versions of Apache Airflow Providers

_No response_

### Deployment

Official Apache Airflow Helm Chart

### Deployment details

_No response_

### Anything else

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

"""A list of columns to show in the Add form.
        This dynamically calculates additional fields from providers and add
        them to the backing list. This calculation is done exactly once (by
        checking we're referencing the class-level variable instead of the
        instance-level), and only after we enter the request context (to skip
        superfuluous checks done by Flask-Appbuilder on startup).
        """
        if self._add_columns is type(self)._add_columns and has_request_context():
            self._add_columns = [*self._add_columns, *(k for k, _ in self._iter_extra_field_names())]
        return self._add_columns
    @property
    def edit_columns(self) -> list[str]:
        """A list of columns to show in the Edit form.
        This dynamically calculates additional fields from providers and add
        them to the backing list. This calculation is done exactly once (by
        checking we're referencing the class-level variable instead of the
        instance-level), and only after we enter the request context (to skip
        superfuluous checks done by Flask-Appbuilder on startup).
        """
        if self._edit_columns is type(self)._edit_columns and has_request_context():
            self._edit_columns = [*self._edit_columns, *(k for k, _ in self._iter_extra_field_names())]
        return self._edit_columns
    @action("muldelete", "Delete", "Are you sure you want to delete selected records?", single=False)
    @auth.has_access(
        [
            (permissions.ACTION_CAN_EDIT, permissions.RESOURCE_DAG),
        ]
    )
    def action_muldelete(self, items):