Dbt-risingwave

- Support rename statement in dbt-risingwave.
- Fix `incremental` model, dbt run with `--full-refresh`.

- Support `incremental` model. You can use `incremental` when you want to have better control of when the table should be updated in a batch way.
- Improve `sink` model, now we can define sink in this way

{{
config(
materialized="sink",
connector="kinesis",
data_format="PLAIN",
data_encode="JSON",
connector_parameters={
"primary_key": "pk,sk",
"stream": var("kinesis_sink")[target.profile_name]["stream"],
"aws.region": var("kinesis_sink")[target.profile_name]["region"],
"aws.credentials.role.arn": var("kinesis_sink")[target.profile_name]["role_arn"],
"aws.credentials.access_key_id": env_var('AWS_ACCESS_KEY_ID', ''),
"aws.credentials.secret_access_key": env_var("AWS_SECRET_ACCESS_KEY", ''),

},
format_parameters={
"force_append_only": true,
},
)
}}

-- do some wrangling here:
SELECT * FROM {{ ref("model1") }}

- Add connection parameter `gssencmode=disable` by default.

- Updated `dbt-core` from `v1.6.0` to `v1.7.0`.
- Improved skip logic for models such as `source`, `table_with_connector`, `sink`, `view`.

v.1.6.1
- change relation_max_name_length from 63 to 1024
- support `on_configuration_change` on `materialized_view` model. Same as PostgreSQL, the configuration only handles indexes at this moment.

- Change `dbt run` default behavior to not drop models. Option `--full-refresh` is needed, if you want to drop models first and then create.
- Use `materialized_view` instead of `materializedview` in model materialization.
- Support new model materializations: `source`, `table_with_connector`, and `sink`. All these materializations need you to provide the create statement as a whole instead of a select query.
- Support model contract.
- Support indexes configuration.

- Support materialization `materializedview`, `table`, `view` and `ephemeral`.