CI: remove dbf from image/env — installed via auto-derive now

With ci.yml's auto-derive step in place (previous commit), dbf is
installed at CI runtime from TMGimporter's .gpr.py requires_mod list.
Keeping it baked into the Dockerfile and environment.yml in parallel
would defeat the "single source of truth = .gpr.py" goal and drift
the moment a new addon declares an additional dep.

Remove dbf from both; leave the stable base (PyGObject, pycairo,
Gramps, orjson, ruff) since those are not addon deps. Add a comment
pointing readers at the auto-derive step so future edits do not
re-bake runtime deps back in.

Author: eduralph

.github/docker/gramps-ci/Dockerfile

@@ -37,13 +37,17 @@ RUN apt-get update && apt-get install -y --no-install-recommends \
         xauth \
     && rm -rf /var/lib/apt/lists/*
 
+# Addon runtime deps (dbf, networkx, lxml, svgwrite, boto3, etc.) are
+# NOT baked in here — ci.yml's "Install addon runtime deps (derived from
+# requires_mod)" step pip-installs them at CI runtime from every
+# .gpr.py's requires_mod list, matching what Gramps' Addon Manager does
+# for an end user. Keeps .gpr.py the single source of truth.
 RUN pip install --no-cache-dir \
         PyGObject \
         pycairo \
         "gramps>=6.0,<6.1" \
         orjson \
-        ruff \
-        dbf
+        ruff
 
 RUN apt-get purge -y gcc python3-dev pkg-config && apt-get autoremove -y
 

.github/environment.yml

@@ -6,7 +6,10 @@ dependencies:
   - pygobject
   - gtk3
   - pip
+  # Addon runtime deps (dbf, networkx, lxml, svgwrite, boto3, etc.) are
+  # installed at CI runtime by ci.yml's auto-derive step from .gpr.py
+  # requires_mod — single source of truth. Keep only the stable base
+  # here (Gramps + orjson for plugin registration).
   - pip:
       - "gramps>=6.0,<6.1"
       - orjson
-      - dbf