Switch pyproject backend to poetry

This makes it easier to consistently handle dependencies and dependency locks.

This should not affect any existing workflows, as pre-commit hooks to update
the lock and export to the requirements_dev.txt should make this mostly
transparent to any existing usage.

It means that it is easier to maintain consistency with the (fully specified
and verified) dependencies as they change.

.github/workflows/build_and_test.yml

@@ -15,7 +15,7 @@ jobs:
       - name: Install dependencies
         run: |
           python -m pip install --upgrade pip
-          pip install pytest build
+          pip install build
       - name: Build distribution
         run: |
           python -m build
@@ -29,7 +29,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.8", "3.9", "3.10", "3.11"]
+        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]
 
     steps:
       - uses: actions/checkout@v3

.pre-commit-config.yaml

@@ -34,3 +34,11 @@ repos:
     - types-requests
     - types-pkg_resources
     - types-pyyaml
+
+- repo: https://github.com/python-poetry/poetry
+  rev: 1.8.0
+  additional_dependencies: ["poetry-plugin-export"]
+  hooks:
+    - id: poetry-lock
+    - id: poetry-export
+      args: [-o, requirements_dev.txt, --with=dev, --without-hashes]