### Description

Auto-refresh is an awesome new feature! Right now it occurs every [3 seconds](https://github.com/apache/airflow/blob/79d85573591f641db4b5f89a12213e799ec6dea1/airflow/www/static/js/tree.js#L463), and this interval is not configurable. Making this interval configurable would be useful.

### Use case/motivation

On a DAG with many tasks and many active DAG runs, auto-refresh can be a significant strain on the webserver. We observed our production webserver reach 100% CPU today when we had about 30 running DAG runs of a DAG containing about 50 tasks. Being able to increase the interval to guard against this would be helpful.

### Related issues

_No response_

### Are you willing to submit a PR?

- [X] 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)

airflow/www/views.py
dag_id,
        task_id,
        origin,
        execution_date,
        upstream,
        downstream,
        future,
        past,
        state,
    ):
        dag = current_app.dag_bag.get_dag(dag_id)
        latest_execution_date = dag.get_latest_execution_date()
        if not latest_execution_date:
            flash(f"Cannot mark tasks as {state}, seem that dag {dag_id} has never run", "error")
            return redirect(origin)
        execution_date = timezone.parse(execution_date)
        altered = dag.set_task_instance_state(
            task_id, execution_date, state, upstream=upstream, downstream=downstream, future=future, past=past
        )
        flash(f"Marked {state} on {len(altered)} task instances")
        return redirect(origin)
    @expose('/confirm', methods=['GET'])
    @auth.has_access(
        [
            (permissions.ACTION_CAN_READ, permissions.RESOURCE_DAG),
            (permissions.ACTION_CAN_EDIT, permissions.RESOURCE_TASK_INSTANCE),
        ]
    )
    @action_logging
    def confirm(self):