delete+insert materialization does not work with location property specified

[yakovlevvs]

Expected behavior

Dbt runs models with delete+insert materialization strategy and specified location consistently

Actual behavior

On the second and subsequent runs model refresh fails with error message:
message="Cannot create a table on a non-empty location: s3a://<location>, set 'iceberg.unique-table-location=true' in your Iceberg catalog properties to use unique table locations for every table.", query_id=<query id>)

Steps To Reproduce

Create a model with following config block and run it two times

    config(
        materialized='incremental',
        incremental_strategy='delete+insert',
        unique_key=['state', 'county', 'city'],
        properties= {
            "format": "'PARQUET'",
            "format_version": "2",
            "location": "'s3a://datalake/model'"
        }
    )

Log output/Screenshots

I think this happens because when we create a temporary table we pass properties block unchanged and Trino tries to create that table on the same location. Maybe if we add __dbt_tmp suffix to the name of temp table, we could patch the location the same way? This would make it's location unique and resolve this issue.

Operating System

Ubuntu 24.04.1 LTS

dbt version

1.9.2

Trino Server version

455

Python version

3.12.3

Are you willing to submit PR?

• Yes I am willing to submit a PR!

[ArtemiyNaumov]

Heavy plus sign to this issue, it has pretty big negative impact on users, which can be confirmed by other issues (example 1, example 2)
Here we also put more detailed description of this problem