Remove pyupgrade from the codebase

[nathanjmcdougall]

This is re-implemented with the UP Ruff rules. Sometimes there is a slight parity lag (i.e. rules exist in pyupgrade that don't exist in Ruff) but that's usually only during the pre-release phase of a new Python version while everyone sorts things out behind-the-scenes.

[ ] Add tests for the change. In general, aim for full test coverage at the Python level. Rust tests are optional.
[ ] Add any appropriate documentation.
[ ] Add a summary of changes to the latest section at the top of CHANGELOG.rst. (If it's not there, add it.)
[ ] Add your name to AUTHORS.rst.
[ ] Run just full-check.

[codspeed-hq]

CodSpeed Performance Report

Merging #286 will not alter performance

_{Comparing nathanjmcdougall:maint/remove-pyupgrade (f2f9739) with main (5899ee0)}

Summary

✅ 26 untouched
⏩ 23 skipped¹

Footnotes

1. 23 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[seddonym]

Nice! Thank you.