ruff check and ruff format github action

[maurycy]

This is very similar to what was done in pyperformance:

• https://github.com/python/pyperformance/blob/main/.pre-commit-config.yaml
• https://github.com/python/pyperformance/blob/main/.github/workflows/lint.yml

ruff check is used since #184, and it's clean:

2026-01-23T20:50:23.718836000+0100 maurycy@gimel /Users/maurycy/work/pyperf (maurycy-ruff-ci) % uvx ruff check
All checks passed!

The PR also adds pre-commit via prek.

[vstinner]

I'm not convinced that ruff format makes the code easier to read/maintain.

@corona10: Do you have an opinion on this change?

[maurycy]

@vstinner Thank you for taking a look.

It's customizable. We can figure out a set of extend-select, extend-ignore etc. flags that minimize the amount of changes, yet enforce some rules.

Some background here: I was thinking about plugging in profiling.sampling over the holidays (the idea was to run all the pyperformance benchmarks with it). The attempt made me realize that's not exactly trivial to do it well but also there's no style to adher to.

I can remove the format part, and leave the rest (ie: pre-commit, Gihub action updates and Dependabot.)

[vstinner]

You should write a separated PR for these changes and the .github/dependabot.yml change.

[maurycy]

@vstinner Thank you. Done in #229

[corona10]

I'm not convinced that ruff format makes the code easier to read/maintain.

I don't have a preference for the formatting tool, but prefer to lean towards matching the same tool with pyperformance as much as possible.