Add variable to allow users to exclude all results columns

[glsdown]

Overview

As can be seen in #369, there are issues where the BQ length gets too large. This has started happening since introducing this column to return all results available in the objects. Therefore, I have added a new variable dbt_artifacts_exclude_all_results which can be set to true to disable this column from being populated.

Ideally, we'd want the default to be to 'not' include this field, but as it's been released with the field included (i.e. opt-in), it doesn't feel right to do that, so I have built it as an opt-out feature.

Update type - breaking / non-breaking

• [ ] Minor bug fix
• [ ] Documentation improvements
• [ ] Quality of Life improvements
• [x] New features (non-breaking change)
• [ ] New features (breaking change)
• [ ] Other (non-breaking change)
• [ ] Other (breaking change)
• [ ] Release preparation

What does this solve?

Outstanding questions

What databases have you tested with?

• [ ] Snowflake
• [ ] Google BigQuery
• [ ] Databricks
• [ ] Spark
• [ ] N/A

[stevenkoppenol]

Great proposal. I hope this will solve the "query too long" error.