### Description

I would greatly appreciate it if the `EcsRunTaskOperator` could incorporate the `deferrable` mode. Currently, this operator significantly affects the performance of my workers, and running multiple instances simultaneously proves to be inefficient. I have noticed that the `KubernetesPodOperator` already supports this functionality, so having a similar feature available for ECS would be a valuable addition.

Note: This feature request relates to the `amazon` provider.

### Use case/motivation

Reduce resource utilisation of my worker when running multiple ecs run task operator in paralllel.

### Related issues

_No response_

### 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)

self.log_fetcher.run()
        self.logger_mock.info.assert_has_calls(
            [
                mock.call("[2021-04-02 21:51:07,123] First"),
                mock.call("[2021-04-02 21:52:47,456] Second"),
                mock.call("[2021-04-02 21:54:27,789] Third"),
            ]
        )
    @mock.patch(
        "airflow.providers.amazon.aws.hooks.logs.AwsLogsHook.get_log_events",
        side_effect=ClientError({"Error": {"Code": "ResourceNotFoundException"}}, None),
    )
    def test_get_log_events_with_expected_error(self, get_log_events_mock):