feat: Use dbt state to avoid large table rebuilds

[bmtcril]

This is a work in progress to avoid rebuilding our large materialized views when we can avoid it. This dbt feature is complicated and requires storing the state of the last run so it can decide what's changed.

Closes: #546

Open questions:

• How to work around this option being automatically added for commands that it doesn't make sense for (maybe just document that it needs to be turned off for them?)
• Is a k8s PVC the right way to go to store the state there?
• Are there other ways to surface that this is happening, or is some documentation enough
• What things should we consider safe to ignore for "changed" state? Tests, probably. Anything else? https://docs.getdbt.com/reference/node-selection/state-comparison-caveats