Check for stale DB on quality gate runs

In v5 and earlier we've had a DB check to ensure our quality gate DB in use was not too out of date. We've removed this since there is no longer enough historical entries to account for this check (3 as opposed to 90). In v6 we should add back a history.json or similar file that we can check against that has more than just the latest entry.

Related to #2036, which takes out the check