AWS system tests: increase Redshift timeouts

[vincbeck]

Similar to #31418. One of our system test executions failed because it timed out while waiting for the cluster to be created. Increasing the timeout should resolve the issue.

Edit: It happens to another of our system test that uses RedshiftClusterSensor. Somehow, Redshift takes more time now to spin clusters up. Thus, I updated all our system tests using RedshiftClusterSensor to set/increase the timeout.

INFO     airflow.task.operators:redshift_cluster.py:64 Poked cluster envfd53fef2-redshift-cluster for status 'available', found status 'creating'
--
ERROR    airflow.task:taskinstance.py:1903 Task failed with exception
Traceback (most recent call last):
File "/opt/airflow/airflow/sensors/base.py", line 242, in execute
raise AirflowSensorTimeout(message)
airflow.exceptions.AirflowSensorTimeout: Sensor has timed out; run duration of 901.579888 seconds exceeds the specified timeout of 900.

---

^ 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.

[vincbeck]

It happened this morning to another of our system test that uses RedshiftClusterSensor. Somehow, Redshift takes more time now to spin clusters up. Thus, I updated all our system tests using RedshiftClusterSensor to set/increase the timeout.

[o-nikolas]

It happened this morning to another of our system test that uses RedshiftClusterSensor. Somehow, Redshift takes more time now to spin clusters up. Thus, I updated all our system tests using RedshiftClusterSensor to set/increase the timeout.

Outside the scope of this PR: We should change the default value for that sensor, if the default is doomed to fail with a timeout then it's not a good user experience.

[vincbeck]

It happened this morning to another of our system test that uses RedshiftClusterSensor. Somehow, Redshift takes more time now to spin clusters up. Thus, I updated all our system tests using RedshiftClusterSensor to set/increase the timeout.

Outside the scope of this PR: We should change the default value for that sensor, if the default is doomed to fail with a timeout then it's not a good user experience.

The default value is actually the default value set by Airflow (1 week), see here. So no need to update the sensor, we were just setting too low timeouts in our system tests