Move 'temporary' tables to a working database

**Is your feature request related to a problem? Please describe.**
'temporary' tables such as the 'new data' table (e.g. `my_table__dbt_new_data_` ), can clutter the main databases causing confusion to users.

**Describe the solution you'd like**
Have an option to create these 'temporary' tables in a separate 'working' database in clickhouse. Ideally we should be able to configure where these tables are created to avoid confusion, and to simplify the clean up of these tables if they are left dangling after a failure.

**Describe alternatives you've considered**
Perhaps a macro to search for such tables and clean them up, but it would be cleaner to separate them in the first place if possible.

No files, tests, or entry points are named. Start by locating the logic that creates temporary tables and the configuration used for database targets. Done means a configurable working database is supported for these tables and cleanup behavior is clear.

Written by the indexing model from the issue text.