Publish yearly detailed FERC1 accounting tables

[cmgosnell]

Overview

Closes #3642.

What problem does this address?

What did you change?

• move where we are cleaning up the aggregate_{ dimension } columns
• add income statement based table table and field schema
• add assets table table and field schema
• add liabilities table table and field schema
• update alembic schema
• clean out cols_to_keep cruft in boom

s# 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.

[aesharpe]

Looks good! Comments are mostly nits that you can ignore if you feel it's OOS or not enough time. One high-level thought is to include more information about what one might expect to find in an assets, liabilities, income statement tables. The descriptions say "this table contains granular accounting data from utilities' XXX" but doesn't go into detail about what that might be.

[aesharpe]

nit: the way "category" and "component" are used here suggests nested categories and components that I think isn't what we're trying to convey. Maybe say: "categorized components of utility revenue requirements"?

[cmgosnell]

"The category of revenue requirement associated with each component of utility's income statements. "?

[aesharpe]

Maybe call out the revenue_requirement_category column by name instead of referencing it by saying "components of a utility's revenue requirement"

[aesharpe]

💛