Consider moving from pre-commit to prek

[Prek](https://prek.j178.dev/)([github](https://github.com/j178/prek)) claims to be a drop-in replacement while being faster and making use of `uv` for creating environments.

While it's still pre 1.0, it has seen fairly wide adoption and is used for cPython and fastapi which seem big enough for it to be around and supported for a while.

It'd be good to try it here and see if it speeds things up at all. I have also seen instances of pre-commit not working if the environment is not activated which this might fix.

Start by locating the repository's current pre-commit configuration and uv setup; no file or test is named in the issue. Compare the existing setup with prek, then verify whether the change improves speed or avoids the reported inactive-environment failure.

由索引模型根據 Issue 內容生成。