Add Q4 2024 CEMS data to ETL

[cmgosnell]

Overview

Closes #4041 .

What problem does this address?

What did you change?

adds new doi
update source partition

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?

I ran the daster assets down and upstream or the hourly emissions table (via *"core_epacems__hourly_emissions"*)/ These assets all generated just fine.

I checked for unit, integration and validation tests. There are unit tests which are passing and not really directly accessing 2024.

I did check the annual row counts and found this (which looks good):

{
    1995: 3846120,
    1996: 3645432,
    1997: 17660784,
    1998: 18073848,
    1999: 22004256,
    2000: 23553696,
    2001: 26200776,
    2002: 30017256,
    2003: 33568728,
    2004: 35335080,
    2005: 35838552,
    2006: 36210960,
    2007: 36405240,
    2008: 40525032,
    2009: 40320840,
    2010: 40499832,
    2011: 40665552,
    2012: 40614648,
    2013: 40114824,
    2014: 39549648,
    2015: 38939616,
    2016: 38027208,
    2017: 36895272,
    2018: 36779712,
    2019: 36301368,
    2020: 35848680,
    2021: 35380968,
    2022: 35166792,
    2023: 34791552,
    2024: 34293936,
}

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]

✔️