👌 Template: switch to Ruff hook from repo for pre-commit

Use the Ruff pre-commit hook from the astral repository, instead of a `local` repo
relying on Hatch. Hatch uses Ruff under the hood anyways, and we don't want contributors
to have to install Hatch. Moreover, using a locally installed Hatch instance has shown
to not always be robust or deterministic in the past, especially in CI.

Some of the `ignore` rules might not make sense at this point, since Ruff does not
`select` them by default. But we keep them and their rationale for now, since we may
introduce their classifier in the future.

`ruff check --fix` can change code semantics/structure (e.g., remove unused imports,
reorder/simplify, apply pyupgrade-like fixes). These edits often need reformatting
afterwards. Hence, we switch the order of the pre-commit to run the linter first.

Author: mbercx

template/.pre-commit-config.yaml.jinja

@@ -1,13 +1,11 @@
 repos:
-- repo: local
-  hooks:
-  - id: format
-    name: Format with Ruff
-    entry: hatch fmt -f
-    language: system
-    types: [python]
-  - id: lint
-    name: Lint with Ruff
-    entry: hatch fmt -l
-    language: system
-    types: [python]
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.13.2
+    hooks:
+      - id: ruff-check
+        name: Lint with Ruff
+        types_or: [ python, pyi ]
+        args: [ --fix ]
+      - id: ruff-format
+        name: Format with Ruff
+        types_or: [ python, pyi ]

template/tests/conftest.py

@@ -2,6 +2,7 @@
 
 Docs: https://docs.pytest.org/en/stable/how-to/fixtures.html#conftest-py-sharing-fixtures-across-multiple-files
 """
+
 import pytest
 
 

template/tests/test_example.py

@@ -1,3 +1,2 @@
-
 def test_example(readability_counts):
     assert readability_counts is True