Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

test(user_monitoring): sync on ingest telemetry to remove timing flake

The "other users metrics" test relied on `:timer.sleep(500)` + `:timer.sleep(1500)`
+ `assert_receive ..., 5_000` to wait for a two-pipeline async chain (Broadway #1
batch_timeout → OtelMetricExporter tick → Broadway #2 batch_timeout → stubbed
bigquery_tabledata_insert_all). Expected latency is ~3s with only ~2s of slack,
which CI exceeded.

Attach to [:logflare, :backends, :ingest] telemetry filtered to other_source so
the test waits on an observable production signal instead of guessed sleeps.
Each remaining assert_receive now corresponds to one pipeline stage, giving
~10s slack on each and clearer failure attribution.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>