[CT-3326] [Regression] Deferral and Retry fail in 1.7 if you don't have a run *without* deferral using 1.7 first

[martynydbt]

Is this a regression in a recent version of dbt-core?

• I believe this is a regression in dbt-core functionality
• I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior

If a user upgrades from anything <1.7 to 1.7, then deferral and dbt retry are going to fail with the error.

Runtime Error
 Expected a schema version of "https://schemas.getdbt.com/dbt/run-results/v5.json" in /tmp/defer-artifacts/run_results.json, but found "https://schemas.getdbt.com/dbt/run-results/v4.json". Are you running with a different version of dbt?

Expected/Previous Behavior

For it to defer or retry successfully after upgrading.

Steps To Reproduce

1. Take a project running a version older than 1.7 and using deferral.
2. Upgrade it to 1.7
3. Re-run a job from a point of failure.

Relevant log output

No response

Environment

- OS:
- Python:
- dbt (working version): anything before 1.7.0
- dbt (regression version): 1.7.0

Which database adapter are you using with dbt?

other (mention it in "Additional Context")

Additional Context

Feedback from @jtcohen6 :

• The way we've handled this for state comparison to date is by adding logic within dbt-core to upgrade older manifests into the now-expected schema.
• We also need to add a test (like this one) to ensure this doesn't break going forward for older schemas of run_results.json