Catalist testing

[bmos]

What is this change?

• Refactor catalist testing to use real files on disk
• Increase coverage of catalist connector
• Sync ruff version between pyproj and pre-commit (it got out of sync during a recent PR, resulting in the pre-commit job and ruff-format job sometimes having different outputs.

Considerations for discussion

• Catalist: Patch Exception Handling #1818 needed this

How to test the changes (if needed)

• (How should a reviewer test this functionality.)

Breaking Changes

Breaking changes are changes to our public API which may require existing users to change their code. If there are no breaking changes, any existing parsons user should not need to do anything after updating their parsons version.

Does this PR introduce breaking changes?

• label: Breaking change — This PR introduces one or more breaking changes.
• label: Non-breaking change — This PR does not introduce one or more breaking changes.

Details (if needed)

• (List out any changes to the API that may cause breaks for developer implementation.)

[bmos]

Oops, seems like updating from main broke something.

[bmos]

Okay, this is ready to be merged @shaunagm.
Once it is, @IanRFerguson's PR should be updated from main and I think it'll pass all the tests.

[ghost]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
parsons/catalist
catalist.py
Project Total

This report was generated by python-coverage-comment-action