ZTL - make sure comparison is to previous version

There's a couple ways to go about this, but we've had a few times now were GIS builds ZTL, but the previous version was never archived with ingest (or even published from draft to publish often, as was the case this time). This often doesn't come up until they've already done some QA, so this has been a big waste of time for them.

There are a few things that would work/help. Worth brainstorming a little as to what feels most appropriate (and maybe check with GIS as well)

1. a data check - check that the "previous" version (latest from edm-recipes) is only one month less than the current version
2. pull from edm-publishing latest instead of ingest (gets rid of a step, though in the case
3. make the versions much more apparent in the qa files (filenames?)
4. make sure that GIS only publishes ZTL from publish folder rather than draft as it seems that they do now (since last month was never published
5. add something of job to the ztl dataloading action that
   • makes sure previous draft was actually published
   • archives ztl from publish-latest into edm-recipes

Start by tracing the ZTL dataloading action and how it uses edm-recipes, edm-publishing, and the draft and publish folders. Compare the proposed data check, source change, QA filenames, and archive steps with the current workflow; done means an agreed approach prevents QA from proceeding against an unavailable or incorrect previous version.