Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Current State
At the moment temp tables created in big query dbt models have arbitrary timeout set to 12h.

Code Reference

Idea for the feature
It would be useful to customize this timeout and align it with actual timeout for processing.

Idea for follow up
Once we customize timeout - it will give us foundation to also customize temp table name and make it per run - at the moment it's always <original-table>_temp which will prevent e.g. concurrent runs targeting different partitions with insert_overwrite per partition strategy.
I think in order to get there though - it's essential to align timeouts.

Describe alternatives you've considered

No response

Who will this benefit?

People who run the same model many times, with high failures rate (since if query fails temp table won't be dropped).

Are you interested in contributing this feature?

Yup, I'll add PR shortly + I signed CLA

Anything else?

No response