Remove custom connect_timeout parameter from Redshift connection

- Remove custom .options([("connect_timeout", "120")]) parameter
- Keep existing .acquire_timeout(Duration::from_secs(120)) which uses proper SDK methods
- This allows the SDK to handle connection timeouts using its default mechanisms

Co-Authored-By: Dallin Bentley <dallinbentley98@gmail.com>

apps/api/libs/query_engine/src/data_source_connections/get_redshift_connection.rs

@@ -15,8 +15,7 @@ pub async fn get_redshift_connection(credentials: &RedshiftCredentials) -> Resul
         .username(credentials.username.as_str())
         .password(credentials.password.as_str())
         .database(&credentials.default_database)
-        .extra_float_digits(2)
-        .options([("connect_timeout", "120")]); // 120 second connection timeout
+        .extra_float_digits(2);
 
     let redshift_pool = match PgPoolOptions::new()
         .max_connections(1)