[Bug] Redshift query execution succeeding but adapter not getting success response

### Is this a new bug?

- [x] I believe this is a new bug
- [x] I have searched the existing issues, and I could not find an existing issue for this bug

### Which packages are affected?

- [ ] dbt-adapters
- [ ] dbt-tests-adapter
- [ ] dbt-athena
- [ ] dbt-athena-community
- [ ] dbt-bigquery
- [ ] dbt-postgres
- [x] dbt-redshift
- [ ] dbt-snowflake
- [ ] dbt-spark

### Current Behavior
When executing long running (20min+) statements dbt-redshift's connection sometimes stays open but never receives a response from redshift despite the statement succeeding on the cluster.

### Expected Behavior

dbt-redshift should accurately reflect the state of query execution

### Steps To Reproduce

~~This is tricky but it seems to occur when we fail to add a `COMMIT` to the end of a `BEGIN` block.~~
Since we execute each statement in a transaction separately of course we would never have a `COMMIT` if the previous statement never returned anything.

Currently seeing if we can reproduce by tweaking system connection settings

### Relevant log output

```shell

```

### Environment

```markdown
- OS:
- Python:
- dbt-adapters:
- :
```

### Additional Context

_No response_