versioning of dcp addresspoints for use in gru qaqc

This maybe belongs in the db-gru-qaqc repo, but putting here for visiblity.

For all datasets, the gru code assumes that they've been archived in recipes with "YY{a-d}" scheme. However, addresspoints doesn't actually follow this scheme (at least in edm-publishing/datasets), it's simply by date.

However, when we ran library in the past, we'd just pull it from the staging folder and manually specify that the version was "24d". Now, new ingest code actually finds the "latest"/max versioned foldername in datasets folder and bases version on that. A little more certainty in terms of what data we're referring to. But now tougher to link dcpaddresspoints to quarterly releases for the sake of gru qaqc.

I think ideally, we add some special import logic in the gru repo (or just in recipes connector), that

1. finds the date of archival of one of the "actual" 24d release datasets (or just uses hardcoded dates - Nov 1 or something for "d") to figure out how fresh data should be
2. uses that date to try to look up a corresponding version of dcp_addresspoints to use, and errors if there's not one within... 1 month? 2 months?

Start by tracing the new ingest code and the recipes connector, then compare how release dataset versions and dcp_addresspoints archival folders are selected. Clarify whether the logic belongs in db-gru-qaqc or this repository, define the date or version matching window and failure behavior, and confirm the result against quarterly releases.