Option to use a manifest for prod model paths (--state)

[dlawin]

Is your feature request related to a problem? Please describe.
A manifest.json is the source of truth for model paths in different environments. Using variables can work in a lot of situations, but not all, especially if I use custom macros to define database names and schema names.

Add a flag similar to dbt's --state to point to a local manifest.json. If this flag is supplied -- use that as the paths for any production models.

This could be extended to pull a manifest from a remote location, but start simple with a local file.

[dlawin]

Possible alternative to #447

[github-actions]

This issue has been marked as stale because it has been open for 60 days with no activity. If you would like the issue to remain open, please comment on the issue and it will be added to the triage queue. Otherwise, it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment and it will be reopened for triage.