[Bug] Fix scenarios where `--empty` flag pushes `limit 0` into metadata queries

[mikealfare]

resolves #1033

Problem

We use {{ relation }} to render the relation name in metadata queries. However, we implemented the --empty flag to add limit 0 when {{ relation }} is used. We wind up with queries like:

describe table (select * from my_relation limit 0)

which is not valid sql.

Solution

• Use {{ relation.render() }} in these scenarios (there are many)
• Add a test case that confirms we can use these macros while using the --empty flag

Implementation

1. Merge this PR demonstrating that these tests work (we`re here)
2. Move the bulk of this PR into dbt-tests-adapter
3. Create a final PR that removes most of this and uses the dbt-tests-adapter tests

Checklist

• [x] I have read the contributing guide and understand what's expected of me
• [x] I have run this code in development and it appears to resolve the stated issue
• [x] This PR includes tests, or tests are not required/relevant for this PR
• [x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[github-actions[bot]]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-snowflake contributing guide.

[pempey]

@mikealfare When might one expect these change in a release? Or is there a way to test these changes on our system before a release?

[pempey]

I will ask my question to a larger audience: @colin-rogers-dbt @McKnight-42 @jtcohen6 When might one expect these change in a release? Or is there a way to test these changes on our system before a release?