chore: update pre-commit hooks

[pre-commit-ci]

updates:

• github.com/charliermarsh/ruff-pre-commit: v0.0.272 → v0.0.275
• github.com/codespell-project/codespell: v2.2.4 → v2.2.5

[henryiii]

pre-commit.ci autofix

[codecov]

Codecov Report

Merging #2532 (e494db0) into main (bb327c7) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted Files	Coverage Δ
src/awkward/_behavior.py	92.47% <ø> (ø)
src/awkward/_do.py	83.64% <ø> (ø)
src/awkward/_nplikes/__init__.py	80.95% <ø> (ø)
src/awkward/_errors.py	79.11% <100.00%> (ø)

[henryiii]

I wonder if we should swap the order of black and Ruff?

[jpivarski]

It was my understanding that black runs before Ruff, which sounds to me like the right order.

• If black fixes any formatting issues that Ruff would complain about, then black should go before Ruff.
• Since black changes the line numbers of issues that Ruff would complain about, and changes the lines on which a # noqa comment is active, black should go before Ruff.
• If Ruff changes the code to fix easy issues (I think it does), and if Ruff's output format is not acceptable to black, then Ruff should go before black.

Only the last consideration implies Ruff → black, and if all three considerations apply, then we'd have to do black → Ruff → black. (In principle, it might never terminate, since the second run of black could move the positions of # noqa comments! But I would think that enough Ruff users are also black users, and black is not very configurable or at least has well-established defaults, that these issues would get resolved by the Ruff community, not by doing something special downstream.)