Update expected eia923 row counts to match new outputs.

[zaneselvans]

Overview

Update expected row counts for EIA-923 tables that were altered through the integration of new EIA-860 & EIA-923 data in our quarterly release.

Testing

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

• Re-ran the ETL locally
• Ran make pytest-minmax-rows to find discrepancies
• Updated the expected row-counts to match. Most were a tiny fraction of a percent.
• gf_eia923 and frc_eia923 were slightly bigger differences -- under expectations by ~0.2% to ~0.3%

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.