[Bug] Full refresh not deleting materialized view with cascade

[Dnirmania]

Is this a new bug in dbt-redshift?

• I believe this is a new bug in dbt-redshift
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

If execute dbt run --models mv1 --full-refresh, dbt try to drop mv with drop materialized view if exists "database"."schema"."mv1"; command

Expected Behavior

If execute dbt run --models mv1 --full-refresh, dbt try to drop mv with drop materialized view if exists "database"."schema"."mv1" cascade; command

Steps To Reproduce

1. Create mv1 materialized view.
2. Create mv2 materialized view on top of mv1.
3. Execute `dbt run --models mv1 --full-refresh.

Relevant log output

No response

Environment

- OS: ubuntu
- Python: 3.10
- dbt-core:  1.7.1
- dbt-redshift:  1.7.1

Additional Context

No response

[dataders]

Closing as I believe this is a dupe of #642. Please correct me if I'm wrong!