[Feature] Better logging when incremental models are run with full-refresh

### Is this your first time submitting a feature request?

- [x] I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
- [x] I have searched the existing issues, and I could not find an existing issue for this feature
- [x] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

### Describe the feature

There is currently no way to tell if an incremental model is being run with `--full-refresh`, which can be especially troublesome when the full refresh is set in the `dbt_project.yml` via something like the below
```yaml
my_project:
marts:
+full_refresh: "{{ target.name != 'prod' }}"
```

The logs just show the below with no mention of full refresh, and they actually seem to imply the opposite, stating that an incremental model was created when in reality a full-refreshed incremental model was created which is very different.
```log
23:42:12 Found 653 models, 3 seeds, 2 operations, 54 snapshots, 689 data tests, 469 sources, 960 macros
23:42:12
23:42:12 Concurrency: 1 threads (target='dev')
23:42:12
23:42:15 1 of 1 START sql incremental model my_schema.my_table ........ [RUN]
23:42:31 1 of 1 OK created sql incremental model my_schema.my_table ... [SUCCESS 1 in 15.12s]
```

I feel there should be a line in the logs saying something like
```log
23:42:03 Running with dbt=1.9.4
23:42:04 Registered adapter: snowflake=1.9.2
23:42:05 Running full refresh
```

or

```log
23:42:15 1 of 1 START sql incremental model my_schema.my_table (full refresh) ........ [RUN]
23:42:31 1 of 1 OK created sql incremental model my_schema.my_table (full refresh) ... [SUCCESS 1 in 15.12s]
```

### Describe alternatives you've considered

_No response_

### Who will this benefit?

This will make development easier for anyone working on incremental models

### Are you interested in contributing this feature?

yes

### Anything else?

_No response_