Add on_table_exists 'replace' option to Starburst/Trino (#4686)

- Added on_table_exists 'replace' option to Starburst/Trino
- Added new author of Starburst/Trino

website/docs/docs/core/connect-data-platform/trino-setup.md

@@ -4,7 +4,7 @@ description: "Read this guide to learn about the Starburst/Trino warehouse setup
 id: "trino-setup"
 meta:
   maintained_by: Starburst Data, Inc.
-  authors: Marius Grama, Przemek Denkiewicz, Michiel de Smet
+  authors: Marius Grama, Przemek Denkiewicz, Michiel de Smet, Damian Owsianny
   github_repo: 'starburstdata/dbt-trino'
   pypi_package: 'dbt-trino'
   min_core_version: 'v0.20.0'

website/docs/reference/resource-configs/trino-configs.md

@@ -97,8 +97,9 @@ The `dbt-trino` adapter supports these modes in `table` materialization, which y
 
 - `rename` — Creates an intermediate table, renames the target table to the backup one, and renames the intermediate table to the target one.
 - `drop` — Drops and re-creates a table. This overcomes the table rename limitation in AWS Glue.
+- `replace` — Replaces a table using CREATE OR REPLACE clause. Support for table replacement varies across connectors. Refer to the connector documentation for details.
 
-The recommended `table` materialization uses `on_table_exists = 'rename'` and is also the default. You can change this default configuration by editing _one_ of these files:
+If CREATE OR REPLACE is supported in underlying connector, `replace` is recommended option. Otherwise, the recommended `table` materialization uses `on_table_exists = 'rename'` and is also the default. You can change this default configuration by editing _one_ of these files:
 - the SQL file for your model
 - the `dbt_project.yml` configuration file