dagit changes for mvp
- add origin_run_ids to JobTick and JobTickData
- fetch origin runs based on tick.origin_run_ids
- when the user hovers a success tick, the label shows origin run ids
- when the user clicks a success tick, the pop up shows the origin runs. so users can go to the runs and find the engine events reported by the monitor sensor. the modal differentiates "Reacted Runs" (open to naming suggestion) vs "Requested Runs" with extra info icons.
- same sensor metadata table but says "sensor does not target a pipeline" in the pipeline tag
- currently the page won't display "latest runs" because
- that part currently means the targeted runs (runs created by the sensor) so it shows a warning to avoid confusion
- backend isn't ready - no easy way to fetch runs that the sensor reacted to and reported back to.
- build graphql layer (probably storage too) for latest reacted runs
- show "Reacted Runs" in "Latest Runs" and differentiate it from "Requested Runs" similar to the tick modal - if the approach makes sense