Given a case like 4.21-e2e-gcp-ovn-techpreview-serial failures where pathological event failures occur like

event happened 22 times, something is wrong: node/ci-op-n4k5r4xl-863c8-shzcl-master-1 hmsg/8a96eaa4fd - reason/ConfigDriftMonitorStopped Config Drift Monitor stopped (05:55:42Z) result=reject

It would be nice to have a tool sippy chat could use to retrieve events_used_for_junits files, potentially using artifact search, and then find intervals related to events and be able to match times with `E2ETest` or `OperatorState` sources of interest to help debug.