Pending Materialized Views issues to make it fully compatible with dbt

Our current implementation of Materialized views still have not been 100% integrated in dbt and a few compatibility issues were raised during development:

## Current status
Main issue in dbt-Core: https://github.com/dbt-labs/dbt-core/issues/12319
| feature | dbt Core 1.X | dbt Core 2.X | Notes |
| ----- | ------------- | ------------- | ------ |
| ref() inside Config() block | 🔴 | 🔴 | * See below |
| Unit-test issue | 🔴 | 🔴 | |
| Lineage chart issue | 🔴 | 🔴 | |

**\* About the ref() issue**
- PR in dbt Core to allow using `ref()` inside the config() block https://github.com/dbt-labs/dbt-core/pull/12965
- Issue in dbt-clickhouse to move the `ref()` into the config: https://github.com/ClickHouse/dbt-clickhouse/issues/644
- PR doing it: https://github.com/ClickHouse/dbt-clickhouse/pull/645

Related:
- https://github.com/dbt-labs/dbt-core/issues/14587

Start by reading dbt-core issue 12319 and the linked dbt-clickhouse issue 644 and pull request 645, then compare them with the current materialized-view implementation. Done means the listed ref(), unit-test, and lineage-chart compatibility issues are resolved for the supported dbt Core versions.

Written by the indexing model from the issue text.