Order of task arguments in task definition causing error when parsing DAG

### Apache Airflow version 3.1.0 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? Some of my DAGs definitions, that are serialized without errors in 2.11.0, are throwing errors when being serialized in 3.0.0. It seems like some argument names and orderings are not being handled correctly by `@task`. More info in the reproduction steps. ### What you think should happen instead? The example DAG in the reproduction steps should be serialized without errors. ### How to reproduce Create the three following files: ```python # example_1.py from airflow.decorators import dag, task @dag() def example_1(): @task def foo(end_date, start_date): ... foo(None, None) example_1() ``` ```python # example_2.py from airflow.decorators import dag, task @dag() def example_2(): @task def foo(start_date, end_date): ... foo(None, None) example_2() ``` ```shell # test.sh docker run \ --rm \ --entrypoint "/bin/bash" \ --volume .:/opt/airflow/dags/ \ "apache/airflow:${1}" \ -c \ " airflow db migrate > /dev/null 2>&1; airflow dags report 2>/dev/null; " ``` Running `./test.sh 2.11.0` successfully serializes both dags, but running `./test.sh 3.0.0` or `./test.sh 3.1.0` only serializes one of the dags: ``` lucas@tiny ~/Desktop/poc % ./test.sh 2.11.0 file | duration | dag_num | task_num | dags ==============+================+=========+==========+========== /example_1.py | 0:00:00.031625 | 1 | 1 | example_1 /example_2.py | 0:00:00.000719 | 1 | 1 | example_2 lucas@tiny ~/Desktop/poc % ./test.sh 3.0.0 file | duration | dag_num | task_num | dags ==============+================+=========+==========+========== /example_1.py | 0:00:00.055614 | 1 | 1 | example_1 /example_2.py | 0:00:00.001864 | 0 | 0 | lucas@tiny ~/Desktop/poc % ./test.sh 3.1.0 file | duration | dag_num | task_num | dags ==============+===…