add censusfips metadata

[cmgosnell]

Overview

Working on #3884.

What problem does this address?

-just add the fips codes metadata

OOS/for this other PR #4019:

• add the extractor and relevant metadata/column mapping
• [working towards] replacing addfips! make pudl.helpers.add_fips_ids work like it does rn but with our newer archived data and doesn't have the error found in Incorrect county FIPS code for Bedford, VA #3531

Documentation

Make sure to update relevant aspects of the documentation.

Tasks

Preview Give feedback

1. Update the release notes: reference the PR and related issues.
2. Update relevant Data Source jinja templates (see docs/data_sources/templates).
3. Update relevant table or source description metadata (see src/metadata).
4. Review and update any other aspects of the documentation that might be affected by this PR.

Testing

How did you make sure this worked? How can a reviewer verify this?

To-do list

Preview Give feedback

1. If updating analyses or data processing functions: make sure to update or write data validation tests (e.g. test_minmax_rows()).
2. Run make pytest-coverage locally to ensure that the merge queue will accept your PR.
3. Review the PR yourself and call out any questions or issues you have.
4. For minor ETL changes or data additions, once make pytest-coverage passes, make sure you have a fresh full PUDL DB downloaded locally, materialize new/changed assets and all their downstream assets and run relevant data validation tests using pytest and --live-dbs.
5. For bigger ETL or data changes run the full ETL locally and then run the data validations using make pytest-validate.
6. Alternatively, run the build-deploy-pudl GitHub Action manually.

[e-belfer]

Going to approve so you can merge this without re-review but the working partitions need to get fixed!

[e-belfer]

Suggested change

	"working_partitions": {"years": sorted(set(range(2011, 2024)))},
	"working_partitions": {"years": sorted(set(2000, range(2011, 2024)))},

[cmgosnell]

this is a good flag! but since for now we are only planning on using the one freshest year i think it should only be 2023

[zaneselvans]

Do we anticipate updating our fipsification to deal with the time variability of these mappings? There'll definitely be inconsistencies in any individual vintage if we apply it across all years of data.

[cmgosnell]

the plan for this issue rn is to effectively replicate addfips which is to say use one vintage. This vintage will be much more recent (2023 instead of addfips most recent 2015). It should be pretty easy with this overall setup to add the additional vintages as a next step.

[e-belfer]

Adding the extractor in here is going to create a horrible loop - you can't merge the archiver PR without having the metadata in PUDL main, and you can't extract the data without having a production archive published or else zenodo-cache-sync will fail. I suppose you could work around this by pinning to your PUDL with the metadata locally, but it'll make it hard for anyone else to reproduce this. So I'd propose splitting the extraction into a separate PR and getting the metadata piece merged in first (which I think is pretty much good to go?).

[cmgosnell]

yes good point! i will remove all the extractor stuff and make a new pr.