add name to build source data export

[damonmcc]

related to #987

most of the commits are cleanup of things I bumped into. the sections below are related to the more significant changes

all builds on this branch

successful nightly QA build

source data versions csv

a human-friendly "name" or "display name" of our input datasets are not things we've had to worry about before and it seems like data from edm-recipes are the ones we should focus on first

added name to the InputDataset model and added get_name() to the ingest_datastore.Connector

one of the new relevant tests is in the integration test file test_plan_load because plan.write_source_data_versions is only used in load.load_source_data_from_resolved_recipe. would like to punt on omptimizing where these things and their tests live

to avoid issues reading old csvs, I held off on improving the column names even though the frequently used publishing.get_source_data_versions() renames the columns

Template DB's source data versions from this branch

Seems like some datasets are old (library?) and don't have a "name" declared. library templates only had an id and a body of text (description) that sometimes had a name in the first line. that's not something worth parsing IMO, per @fvankrieken suggestion they'll be NULL

FacDB source data versions from this branch

FacDB cli

before

cli arg wasn't being used. tried to do run_pipelines for non-existing dataset named a_name and it tried to run all pipelines declared in datasets.yml

after

[codecov]

Codecov Report

❌ Patch coverage is 94.11765% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 74.26%. Comparing base (a9bce9d) to head (032540a).
⚠️ Report is 9 commits behind head on main.

Files with missing lines	Patch %	Lines
dcpy/lifecycle/builds/plan.py	92.30%	0 Missing and 1 partial ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
dcpy/connectors/ingest_datastore.py	100.00% <100.00%> (ø)
dcpy/lifecycle/builds/load.py	85.48% <ø> (ø)
dcpy/models/lifecycle/builds.py	98.03% <100.00%> (+0.01%)	⬆️
dcpy/models/lifecycle/ingest.py	96.73% <100.00%> (+0.02%)	⬆️
dcpy/lifecycle/builds/plan.py	88.88% <92.30%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[alexrichey]

nit: if you have a sec, this should be a fixture that adds the env var, yields, then pops the env var

[alexrichey]

Good stuff! a few questions, but LGTM. You might try planning/loading a few recipes, in particular maybe the factfinder recipe_qa.py

[fvankrieken]

too many loads here?

On that note, can you also run a nightly qa on this branch just as a sanity check

[damonmcc]

nightly qa run successful (minus CDBG for unrelated reasons and PLUTO taking forever)

[fvankrieken]

🙏

[damonmcc]

actually I must've done this when I was still hoping to change the csv's column names, but I kept the old ones

would prefer to keep the old ones for now (of course adding a new one) and change em later

for posterity before the rebase blast them away, was gonna make them dataset_id, dataset_name, version, file_type

[fvankrieken]

Fair but also sad