Add a CI job that runs linting and formatting against latest ruff

[waxlamp]

This is an experimental idea based off of the work in #2053, which pins Ruff to a specific minor version so that dev and CI don't go out of sync. The idea is to give CI the ability to run against latest Ruff and let the failure of that run indicate new rules, etc., that we may want to adopt by fixing those errors and re-pinning the version used in the "real" runs.

[waxlamp]

Since this PR was spun out from #2053, I'm copying over the comments I left regarding this experiment:

---

see if this actually works

So, it works, but in a way that is kind of useless: the ruff-latest test fails inside its run (as expected) but the job shows a green checkmark in the results panel. Not sure if there's a better thing here (something that shows the failure but doesn't fail the run).

@danlamanna, @jjnesbitt, @mvandenburgh: would this be better as a nightly test? That would require duplicating the GH Action spec (which is a negative) but we could allow it to fail freely without compromising the ability to merge PRs, etc.

[waxlamp]

see if this actually works

So, it works, but in a way that is kind of useless: the ruff-latest test fails inside its run (as expected) but the job shows a green checkmark in the results panel. Not sure if there's a better thing here (something that shows the failure but doesn't fail the run).

@danlamanna, @jjnesbitt, @mvandenburgh: would this be better as a nightly test? That would require duplicating the GH Action spec (which is a negative) but we could allow it to fail freely without compromising the ability to merge PRs, etc.

Dan pointed out that even with a nightly run, alarm fatigue will set in. A better approach would be for us to just pay attention and run against latest Ruff when new versions come out.

I will try converting this to use the "workflow dispatch" mode which would avoid alarm fatigue, but make it a bit easier to actually run against the latest version.

[waxlamp]

Closing this in favor of #2045 and #2057. the pre-commit autoupdate command can be used to upgrade hook versions in lieu of the mechanisms proposed in this PR.