Expand guidance on late-rendering for hooks

[jtcohen6]

Contributions

• I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/reference/resource-configs/pre-hook-post-hook
https://docs.getdbt.com/docs/building-a-dbt-project/dont-nest-your-curlies#an-exception

What part(s) of the page would you like to see updated?

This is one of my least favorite things in dbt. It should not be considered a "happy path." And yet we get issues about it all the time:

• Post-hook doesn't resolve custom schema dbt-core#4023 (comment)
• [CT-1506] [Bug] Nested {{ this }} not working as expected within macro dbt-core#6249 (comment)
• [CT-1634] [Bug] Post-hook in dbt_project.yml using {{ this }} failing to insert table name dbt-core#6411 (comment)
• [CT-2004] [Bug] Insert statement in Post hook not working as expected dbt-core#6837 (comment)
• [CT-2338] [Bug] {{this}} evaluates incorrectly with Snowflake when used in a macro dbt-core#7237 (comment)
• [Bug] Pre- and post-hooks use parse phase values during the execution phase dbt-core#10148 (comment)
• ... (among others) ...

Specifically, if you want to:

• include a {{ ref() }} or {{ source() }} call within a hook
• access {{ this.type }} inside a hook
• call a macro within a hook
• conditionally set and use a variable inside a hook

It would be great, during dbt-core issue triage, to have a clear set of documentation (with examples) to pass along. Even though this is not a pattern we recommend, exactly, it does unlock some intermediate/advanced use cases for a handful of users.

Additional information

No response