### Description

expanding tasks in batches to allow mapped tasks spawn more than 1024 processes.

### Use case/motivation

Maximum length of a list is limited to 1024 by `max_map_length (AIRFLOW__CORE__MAX_MAP_LENGTH)`.
during scheduling of the new tasks, an UPDATE query is ran that tries to set all the new tasks at once.  Increasing `max_map_length` more than 4K makes airflow scheduler completely unresponsive.

Also, Postgres throws `stack depth limit exceeded` error which can be fixed by updating to a newer version and setting `max_stack_depth` higher. But it doesn't really matter because airflow scheduler freezes up.
 
As a workaround, I split the dag runs into subdag runs which works but it would be much nicer if we didn't have to worry about exceeding  `max_map_length`. 

### Related issues

It was discussed here:
[Increasing 'max_map_length' leads to SQL 'max_stack_depth' error with 5000 dags to be spawned #28478](https://github.com/apache/airflow/discussions/28478)

### Are you willing to submit a 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)

try:
            expanded_ti_count: int | None = task.get_mapped_ti_count(self.run_id, session=session)
        except NotMapped:
            expanded_ti_count = None
        
        
        
        context = {
            "conf": conf,
            "dag": dag,
            "dag_run": dag_run,
            "data_interval_end": timezone.coerce_datetime(data_interval.end),
            "data_interval_start": timezone.coerce_datetime(data_interval.start),
            "ds": ds,
            "ds_nodash": ds_nodash,
            "execution_date": logical_date,
            "expanded_ti_count": expanded_ti_count,
            "inlets": task.inlets,
            "logical_date": logical_date,
            "macros": macros,
            "next_ds": get_next_ds(),
            "next_ds_nodash": get_next_ds_nodash(),
            "next_execution_date": get_next_execution_date(),
            "outlets": task.outlets,
            "params": validated_params,
            "prev_data_interval_start_success": get_prev_data_interval_start_success(),
            "prev_data_interval_end_success": get_prev_data_interval_end_success(),
            "prev_ds": get_prev_ds(),
            "prev_ds_nodash": get_prev_ds_nodash(),
            "prev_execution_date": get_prev_execution_date(),