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

del cls.dag
        del cls.hook
    @mock_rds
    def test_poke_true_instance(self):
        """
        By default RdsDbSensor should wait for an instance to enter the 'available' state
        """
        _create_db_instance(self.hook)
        op = RdsDbSensor(
            task_id="instance_poke_true",
            db_identifier=DB_INSTANCE_NAME,
            aws_conn_id=AWS_CONN,
            dag=self.dag,
        )
        assert op.poke(None)
    @mock_rds
    def test_poke_false_instance(self):
        _create_db_instance(self.hook)
        op = RdsDbSensor(
            task_id="instance_poke_false",
            db_identifier=DB_INSTANCE_NAME,
            target_statuses=["stopped"],
            aws_conn_id=AWS_CONN,
            dag=self.dag,
        )
        assert not op.poke(None)
    @mock_rds
    def test_poke_true_cluster(self):