EIA 176 wide tables - follow-up fixes

[jdangerx]

Overview

Fixes a few things from the original PR (#3590):

• the _core_eia176__data multi-asset now has named Outputs - not sure how Dagster was associating these correctly before
• made all the assets in the _core_eia176_ namespace so that it's clear we don't persist them yet
• asset checks now succeed: work around some "expected" diffs

My changes on top of the original PR are all in this commit

TODO in future follow-ups:

• refactor so we only use the aggregate data to cross-check the company data - it doesn't seem that useful to have both the aggregated & disaggregated tables around. Especially if the aggregated data has a bunch of incorrect data floating around in it.
• add the tables to the database, by adding them to db schema and hooking them up to the pudl_io_manager.
• rename the columns to something more useful than the alphanumeric soup they are now
• Update EIA-176 data source documentation

Documentation

Make sure to update relevant aspects of the documentation.

Tasks

Beta 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

Beta 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. Alternatively, run the build-deploy-pudl GitHub Action manually.

[zaneselvans]

Looks good. Materialized fine locally. I did notice that there's no 2023 data for EIA-176 and then found catalyst-cooperative/pudl-archiver#484.

Just one tiny naming thing -- I don't think we've ever applied the "not ready for primetime" underscore prefix to the asset group names. I get the analogy, but it feels like an extra complication that we might forget to undo, when the assets in the group are finally ready.

[zaneselvans]

As far as I know we haven't used the underscore prefix for any of the other asset groups. I think just having the prefix on the assets themselves is probably sufficient to indicate that they are not yet ready for use? Then the asset group will show up in a more expected place in the list of groups, alphabetically.

[zaneselvans]

I went ahead and made this 1-character change in order to get this merged in before I leave.

[zaneselvans]

(and also re-materialized the eia176 assets locally just to make sure nothing weird happened)