Dbt-dry-run

Bugfixes & Improvements

- Added command line flag `--skip-not-compiled` which will override the default behaviour of raising a `NotCompiledExceptipon`
if a node is in the manifest that should be compiled. This should only be used in certain circumstances where you want
to skip an entire section of your dbt project from the dry run. Or if you don't want to dry run tests

- Added `status` to the report artefact which can be `SUCCESS`, `FAILED`, `SKIPPED`

Bugfixes & Improvements

- Add support for dbt 1.4

Bugfixes & Improvements

- Add support for INTERVAL and JSON types.

- Improved error handling when parsing the predicted schema of the dry run queries. Error message will now raise an
`UnknownSchemaException` detailing the field type returned by BigQuery that it does not recognise

Bugfixes

- Don't dry run nodes that are disabled

Bugfixes

- Move column specification to `dry_run_columns` in `external` to avoid conflict with `dbt-external-tables` and other
dbt integrations

Improvements & Bugfixes

- Support dry running tests. Generic and custom tests will be checked. This can catch errors such as column name typos in the
generic test metadata and SQL syntax errors in custom tests

- Added support for `dbt-external-tables`. Any `source` marked with `external` will be 'dry runned' by reading the
schema from the yaml metdata for the source. The dry run does not support schema prediction for external tables