Make it possible to pass another sources dict to DataSource

[e-belfer]

Overview

Addresses a lightweight version of catalyst-cooperative/pudl-archiver#499 in concert with catalyst-cooperative/pudl-archiver#506.

What problem does this address?

In the pudl-archiver repository, we want to make it possible to archive datasets that will never end up in the PUDL repository. Eventually, we'll want to fully separate these two repositories, which raises bigger questions about where the metadata should be defined, etc. But for now, we want to make it possible to add a dictionary of NON_PUDL_SOURCES to the pudl-archiver repository, to be called in a method similar to from_pudl_metadata in frictionless.py.

What did you change?

This method imports the DataSource.from_id() method from PUDL, which currently hardcodes SOURCES into the method. In order to make it possible to provide an alternative dictionary of source metadata into this method, I have added a sources parameter to this method which defaults to SOURCES, but can take a different SOURCE dictionary.

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]

This doesn't get called in pudl-archiver, so I could revert this change. Just figured for consistency it'd make sense to have the same behavior as below.

[zschira]

I think consistency here is good

[e-belfer]

Oops! This crossed over from another branch, I'll remove this.

[zschira]

This seems like a reasonable/simple solution to avoid cluttering our main metadata collection