[CT-2904] [Bug] Should clone with --full-refresh respect the model config?

### Is this a new bug in dbt-core?

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

### Current Behavior

given the config:

```{{
config(
materialized = 'incremental',
unique_key = 'event_key',
on_schema_change = 'fail',
incremental_strategy = 'delete+insert',
transient=false,
full_refresh=false,
)
}}
```

when using the `dbt clone -s --full-refresh` - the model is cloned.

### Expected Behavior

Not sure what I'd want here. Personally I was pleased to see it not respected.. but it probably should be? Or it's a mix of concepts and it should be some `--force` flag or something with `dbt clone` to say "I don't care that it exists, clone it"

### Steps To Reproduce

create an incremental model..

set full_refresh=false in it's config..

run dbt clone --full-refresh.

### Which database adapter are you using with dbt?

dbt-snowflake==1.6.0