Dbt-dry-run

Bugfixes & Improvements

- Added `--extra-check-columns-metadata-key` CLI option. Specifying this will mean that you can use another metadata
key instead of just `dry_run.check_columns`. `dry_run.check_columns` will always take priority over the extra key.
This is useful if you have an existing metadata key such as `governance.is_odp` that you want to enable metadata
checking for

- Added `--version` CLI option to print the installed version of `dbt-dry-run`

- Added support for Python 3.11 ([zachary-povey](https://github.com/zachary-povey))

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