Keep test daemons out of production's traces and database (#87)

The browser suite's daemon took its environment from the shell running
it, so a shell with OTEL_EXPORTER_OTLP_ENDPOINT set would have sent its
fixture scans to production's Tempo, and one with IPX_DATABASE_URL set
would have run the suite against production's database. Both are now
blanked for it. Production's traces carry
deployment.environment.name=production, which the dashboard filters on,
so a daemon run by hand stays out as well.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docker-compose.yml

@@ -10,6 +10,8 @@ services:
       IPX_LOG: "ipx=info"
       # Traces to Tempo, in the monitoring project; ipx sends none without it.
       OTEL_EXPORTER_OTLP_ENDPOINT: "http://192.168.1.130:4318"
+      # What the dashboard filters on, so a daemon run by hand for testing stays out of it.
+      OTEL_RESOURCE_ATTRIBUTES: "deployment.environment.name=production"
     # IPX_DATABASE_URL=postgres://... to use Postgres; without it, /data/state.db (SQLite).
     env_file:
       - ipx.env   # relative: Arcane resolves it inside its own container