### Description

Currently some code in RDS Operators use boto waiters and some uses a custom `_await_status`, the former is preferred over the later (waiters are vetted code provided by the boto sdk, they have features like exponential backoff, etc). See [this discussion thread](https://github.com/apache/airflow/pull/27076#discussion_r997325535) for more details/context.

### Use case/motivation

_No response_

### 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,
        *,
        export_task_identifier: str,
        wait_for_completion: bool = True,
        aws_conn_id: str = "aws_default",
        **kwargs,
    ):
        super().__init__(aws_conn_id=aws_conn_id, **kwargs)
        self.export_task_identifier = export_task_identifier
        self.wait_for_completion = wait_for_completion
    def execute(self, context: Context) -> str:
        self.log.info("Canceling export task %s", self.export_task_identifier)
        cancel_export = self.hook.conn.cancel_export_task(
            ExportTaskIdentifier=self.export_task_identifier,
        )
        if self.wait_for_completion:
            self._await_status(
                "export_task",
                self.export_task_identifier,
                wait_statuses=["canceling"],
                ok_statuses=["canceled"],
            )
        return json.dumps(cancel_export, default=str)
class RdsCreateEventSubscriptionOperator(RdsBaseOperator):