replace pyupgrade isort and black with ruff format

[zacharyburnett]

This PR replaces the pre-commit checks for pyupgrade, isort, and black with ruff format

Checklist

• added entry in CHANGES.rst under the corresponding subsection
• updated relevant tests
• updated relevant documentation
• updated relevant milestone(s)
• added relevant label(s)
• ran regression tests, post a link to the Jenkins job below. How to run regression tests on a PR

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Files	Coverage Δ
romancal/resample/gwcs_drizzle.py	80.68% <ø> (ø)
romancal/skymatch/skymatch.py	80.22% <ø> (ø)
romancal/ramp_fitting/ramp_fit_step.py	31.70% <0.00%> (-0.82%)	⬇️

... and 2 files with indirect coverage changes

📢 Thoughts on this report? Let us know!

[WilliamJamieson]

In order to actually make this a replacement for all the claimed tools, the rule sets for isort, etc have to be enabled in the pyproject.toml file. Those are not part of the default rule set.

[schlafly]

This looks fine to me, and I'm probably in favor of fewer moving pieces, which seems to be the goal of this PR.

But I do think we want to ~settle on some choice of code formatting, etc., and not mess with it very often. Does this represent that choice?

[zacharyburnett]

This looks fine to me, and I'm probably in favor of fewer moving pieces, which seems to be the goal of this PR.

But I do think we want to ~settle on some choice of code formatting, etc., and not mess with it very often. Does this represent that choice?

We can configure ruff format a bit more than we can Black, namely line length, quote character, indent style, etc.: https://docs.astral.sh/ruff/formatter/#configuration

[WilliamJamieson]

This still is not selecting the rules for ruff to replace the pre-commit tooling this PR claims to be replacing. I'll open a PR against your branch fixing these issues.