fix(lva-peripheral): pass GPIO/SPI GIDs to the peripheral container

docker compose's ``group_add`` resolves names against the container's
/etc/group, but the python:slim base used by the respeaker peripheral
doesn't define ``gpio`` or ``spi``. Container start failed with
``Unable to find group gpio: no matching entries in group file``,
which then cascaded into HA reporting ``Unable to connect to the
ESPHome device`` because LVA's ESPHome API never came up.

Pass numeric GIDs with sensible defaults for a stock Raspberry Pi OS
install (gpio=986, spi=989); users on other distros can override via
.env.

Caught during the first hardware smoke test on a Pi 3 + ReSpeaker
2-Mic HAT v2. Same fix has already landed upstream on the LVA branch
(genericJE/linux-voice-assistant feat/peripheral-led-light-entity)
in commit f200720, so this only patches PiCompose's own deployment
copy of docker-compose.yml.

Author: genericJE

03-stage-lva-2mic-peripheral/01-lva-peripheral/files/lva-peripheral/docker-compose.yml

@@ -89,9 +89,13 @@ services:
     devices:
       - /dev/spidev0.0:/dev/spidev0.0
       - /dev/gpiochip0:/dev/gpiochip0
+    # group_add resolves names against the container's /etc/group, but the
+    # python:slim base doesn't define gpio or spi. Pass numeric GIDs so they
+    # match the host's groups instead. Defaults match a stock Raspberry Pi OS
+    # install (check yours with ``getent group gpio spi`` on the host).
     group_add:
-      - gpio
-      - spi
+      - "${GPIO_GID:-986}"
+      - "${SPI_GID:-989}"
     environment:
       - PYTHONUNBUFFERED=1
     command: