Modernize importlib usage

[zaneselvans]

PR Overview

• Updates our usage of importlib.resources to use the current API in a uniform and relatively simple way across the repo. Previously we had a mix of old deprecated functions and an unnecessarily complex syntax from the new API. In almost all cases we can simply use the Traversable class and its pathlib.Path like interface.
• Also avoids use of the deprecated pkg_resources module which is going to be removed from the standard library in Python 3.12, replacing it with functionality from importlib.metadata

PR Checklist

• Merge the most recent version of the branch you are merging into (probably dev).
• All CI checks are passing. Run tests locally to debug failures
• Make sure you've included good docstrings.
• For major data coverage & analysis changes, run data validation tests
• Include unit tests for new functions and classes.
• Defensive data quality/sanity checks in analyses & data processing functions.
• Update the release notes and reference reference the PR and related issues.
• Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.

[zaneselvans]

Note that nearly everything in this documentation page is outdated, since we've moved to using pyproject.toml exclusively to define our packaging.

[jdangerx]

Good point, I think we can just rip out the whole setup.py section. I feel like we're not doing anything so outré with the pyproject.toml that we need special documentation on how to use it, TBH.

[zaneselvans]

Unsure of why this warning is still coming up. Maybe from an imported package? I don't think we're directly using any of the pkg_resources versions now.

[jdangerx]

I poked around a bit and saw some old pkg_resources deprecation warnings from the google SDK libaries.

[codecov]

Codecov Report

Patch coverage: 76.0% and no project coverage change.

Comparison is base (e9735a2) 88.4% compared to head (100f87f) 88.4%.
Report is 4 commits behind head on dev.

Additional details and impacted files

@@          Coverage Diff          @@
##             dev   #2759   +/-   ##
=====================================
  Coverage   88.4%   88.4%           
=====================================
  Files         89      89           
  Lines      10199   10192    -7     
=====================================
- Hits        9024    9018    -6     
+ Misses      1175    1174    -1     

Files Changed	Coverage Δ
src/pudl/analysis/ferc1_eia_train.py	52.9% <0.0%> (-0.4%)	⬇️
src/pudl/transform/eia.py	97.2% <ø> (ø)
src/pudl/transform/ferc1.py	96.8% <50.0%> (+<0.1%)	⬆️
src/pudl/workspace/setup.py	84.1% <50.0%> (+2.5%)	⬆️
src/pudl/analysis/ferc1_eia.py	98.5% <100.0%> (-0.1%)	⬇️
src/pudl/extract/dbf.py	89.4% <100.0%> (ø)
src/pudl/extract/excel.py	94.6% <100.0%> (-0.1%)	⬇️
src/pudl/glue/ferc1_eia.py	98.4% <100.0%> (ø)
src/pudl/helpers.py	87.0% <100.0%> (ø)
src/pudl/output/sql/helpers.py	100.0% <100.0%> (ø)

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jdangerx]

This is nice, thanks for cleaning it up! I'm ok with the codecov patch coverage warning.

[jdangerx]

Nice!

[jdangerx]

Good point, I think we can just rip out the whole setup.py section. I feel like we're not doing anything so outré with the pyproject.toml that we need special documentation on how to use it, TBH.

[jdangerx]

I poked around a bit and saw some old pkg_resources deprecation warnings from the google SDK libaries.