Integrate 2023 EIA 860 Early Release

[cmgosnell]

Overview

Closes #3676.

What problem does this address?

What did you change?

Testing

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

To-do list

Beta Give feedback

1. Update the release notes: reference the PR and related issues.
2. Review the PR yourself and call out any questions or issues you have
3. If updating analyses or data processing functions: make sure to update or write data validation tests (e.g., test_minmax_rows())
4. Ensure docs build, unit & integration tests, and test coverage pass locally with make pytest-coverage (otherwise the merge queue may reject your PR)
5. 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.
6. For significant ETL, data coverage or analysis changes, once make pytest-coverage passes, ensure the full ETL runs locally and run data validation tests using make pytest-validate (a ~10 hour run). If you can't run this locally, run the build-deploy-pudl GitHub Action (or ask someone with permissions to). Then, check the logs on the #pudl-deployments Slack channel or gs://builds.catalyst.coop.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[e-belfer]

A bunch of relatively minor comments on naming conventions. Currently running the assets locally, no problem so far.

[e-belfer]

Looks good, if all the tests pass on your end go ahead and merge!