Test dev dbt image

[sydneynotthecity]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with the jira ticket associated with the PR.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated the README with the added features, breaking changes, new instructions on how to use the repository.

What

Releasing dbt model updates, which contain material schema changes to *_current and enriched_* tables

Note: The two state tables will need to be fully refreshed so that columns backfill. This is manual and requires the deployer to set dbt_full_refresh_models to true in Airflow variables. This is easiest to set in the UI, let the models complete and then set the keys back to false.

Enriched history tables can be backfilled when convenient since these tables are so large. Fully refreshing the model does not work without chunking the tables

Why

Keep curated and aggregate tables aligned with data model changes from protocol releases

Known limitations