fix: Install debugpy in container instead of adding it

Running `uv add debugpy` in the container modifies pyproject.toml and
uv.lock so `git describe` reports local changes in the repo and appends
a `dev0+g<commit>.d<date>` suffix to the version used for the blueapi in
the container

Using `uv pip install debugpy` makes it available in the environment
without modifying any tracked files.

This has to be run after the `uv sync` to stop it being removed again.

Author: tpoliaw

Dockerfile

@@ -7,7 +7,7 @@ RUN apt-get update -y && apt-get install -y --no-install-recommends \
     graphviz \
     && apt-get dist-clean
 
-# Install helm for the dev container. This is the recommended 
+# Install helm for the dev container. This is the recommended
 # approach per the docs: https://helm.sh/docs/intro/install
 RUN curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3; \
     chmod 700 get_helm.sh; \
@@ -27,12 +27,12 @@ RUN chmod o+wrX .
 # Tell uv sync to install python in a known location so we can copy it out later
 ENV UV_PYTHON_INSTALL_DIR=/python
 
-RUN uv add debugpy
-
 # Sync the project without its dev dependencies
 RUN --mount=type=cache,target=/root/.cache/uv \
     uv sync --locked --no-editable --no-dev --managed-python
 
+RUN uv pip install debugpy
+
 # The runtime stage copies the built venv into a runtime container
 FROM ubuntu:resolute AS runtime