Upgrade Poetry, relock lockfile (#435)

* Updates Poetry to 1.4.0 in the container
* Uses "CI method" for downloading and using Poetry
* Update `pyproject.toml` to use the new way of managing dependency groups
  - `tool.poetry.dev-dependencies` is deprecated in favor of using "groups" for management
* Re-lock `poetry.lock`, pinning all dependencies to the latest version allowed by `pyproject.toml`
* Enable `pydantic.mypy` plugin so that mypy upgrade is successful

Author: grahamalama

Dockerfile

@@ -11,14 +11,15 @@ ENV PIP_NO_CACHE_DIR=off \
 ENV PATH="$POETRY_HOME/bin:$PATH"
 
 # Install Poetry - respects $POETRY_VERSION & $POETRY_HOME
-ENV POETRY_VERSION=1.3.2
-RUN curl -sSL https://install.python-poetry.org | python3 -
+RUN python3 -m venv $POETRY_HOME && \
+    $POETRY_HOME/bin/pip install poetry==1.4.0 && \
+    $POETRY_HOME/bin/poetry --version
 
 # We copy our Python requirements here to cache them
 # and install only runtime deps using poetry
 WORKDIR $PYSETUP_PATH
 COPY ./poetry.lock ./pyproject.toml ./
-RUN poetry install --no-dev --no-root
+RUN $POETRY_HOME/bin/poetry install --without dev --no-root
 
 # `production` stage uses the dependencies downloaded in the `base` stage
 FROM python:3.11.2-slim as production

Makefile

@@ -37,7 +37,7 @@ clean:
 install: $(INSTALL_STAMP)
 $(INSTALL_STAMP): poetry.lock
 	@if [ -z $(shell command -v poetry 2> /dev/null) ]; then echo "Poetry could not be found. See https://python-poetry.org/docs/"; exit 2; fi
-	POETRY_VIRTUALENVS_IN_PROJECT=1 poetry install --no-root
+	POETRY_VIRTUALENVS_IN_PROJECT=1 poetry install --with dev --no-root
 	touch $(INSTALL_STAMP)
 
 .PHONY: build