Fix xdist_group: Add --dist=loadgroup to pytest commands

The @pytest.mark.xdist_group markers were being ignored because
pytest-xdist uses --dist=load by default, which doesn't respect groups.

With --dist=loadgroup, tests in the same xdist_group run sequentially
on the same worker, preventing telemetry state interference between
tests.

This is the ROOT CAUSE of the 88 vs 60 events issue - tests were
running in parallel across workers instead of sequentially on one
worker as intended.

Signed-off-by: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: msrathore-db

.github/workflows/integration.yml

@@ -57,6 +57,7 @@ jobs:
       - name: Run e2e tests (excluding daily-only tests)
         run: |
           # Exclude telemetry E2E tests from PR runs (run daily instead)
+          # Use --dist=loadgroup to respect @pytest.mark.xdist_group markers
           poetry run python -m pytest tests/e2e \
             --ignore=tests/e2e/test_telemetry_e2e.py \
-            -n auto
+            -n auto --dist=loadgroup

.github/workflows/test-telemetry-only.yml

@@ -53,4 +53,5 @@ jobs:
 
       - name: Run telemetry test only (with xdist auto to mimic real CI)
         run: |
-          poetry run python -m pytest tests/e2e/test_concurrent_telemetry.py::TestE2ETelemetry::test_concurrent_queries_sends_telemetry -n auto -v -s
+          # Use --dist=loadgroup to respect @pytest.mark.xdist_group markers
+          poetry run python -m pytest tests/e2e/test_concurrent_telemetry.py::TestE2ETelemetry::test_concurrent_queries_sends_telemetry -n auto --dist=loadgroup -v -s