Fix region argument in MappedOperator based on AwsBaseOperator / AwsBaseSensor

[Taragolis]

Originally reported in Slack

Hi everyone! :nyanparrot:
I just upgraded the airflow packages versions:

apache-airflow==2.8.3
apache-airflow-providers-amazon==8.19.0

And now I have a broken DAG:

Broken DAG: [/opt/airflow/dags/distributor_catalogue.py]
Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.11/site-packages/airflow/models/baseoperator.py", line 265, in partial
    validate_mapping_kwargs(operator_class, "partial", kwargs)
  File "/home/airflow/.local/lib/python3.11/site-packages/airflow/models/mappedoperator.py", line 117, in validate_mapping_kwargs
    raise TypeError(f"{op.__name__}.{func}() got {error}")
TypeError: EcsRunTaskOperator.partial() got an unexpected keyword argument 'region'

The use of region is this one:

EcsRunTaskOperator.partial(
    task_id="task_id",
    aws_conn_id="aws_manual_test",
    cluster="tf_ecs_airflow",
    task_definition="tf_ecs_airflow",
    launch_type="FARGATE",
    region="eu-west-3",
    network_configuration={
        "awsvpcConfiguration": {
            "securityGroups": [Variable.get("ecs_securitygroup")],
            "subnets": [Variable.get("ecs_subnet1"), Variable.get("ecs_subnet2"), Variable.get("ecs_subnet3")],
            "assignPublicIp": "ENABLED",
        },
    },
    trigger_rule="all_done",
    waiter_delay=60,
    waiter_max_attempts=3000,
).expand(overrides=generate_params_list)

Does someone know why it is broken?
Thanks a lot 🥹 (edited)

---

This happen because partial check signature, and if argument not exists in any MRO references it will failed.
We grab region directly from kwargs and remove it, for avoid provide it into the BaseOperator.

Fix pretty simple, add region into AwsBaseOperator / AwsBaseSensor signatures, it should fix all operators which migrated to this helper operators and use deprecated region attribute over Dynamic Task Mapping

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[Taragolis]

Yeah... full test works fine. Except mypy, but it not related to this PR

[Taragolis]

Fingers crossed, seems like this test should work (without side effects)