build: evaluate migrating from pre-commit to prek

[hasansezertasan]

Context

prek is a faster, Rust-based, drop-in reimplementation of pre-commit — no Python bootstrap, single binary, reuses the existing .pre-commit-config.yaml.

This is a proposal / discussion issue, not a commitment.

Why consider it

• Faster hook runs & install, no separate Python env for the runner
• Aligns with the uv / Rust-tooling direction (build: migrate from PDM to uv #18)
• Config-compatible, so migration risk is low

Risks / open questions

• Maturity vs. pre-commit; ecosystem familiarity for external contributors
• CI action availability & caching story
• Does every current hook resolve under prek?

Proposed tasks

• Trial prek run --all-files against the current config
• Compare local + CI runtime
• Decide: adopt / defer / reject (document rationale here)