ci_run_n_monitor: pipeline finding unreliable
Ever since !25153 (merged) and the related no-mr-fork-pipelines change, the script is unreliable and slow for me. When I push to an MR and run the script, it often times out looking for it in mesa/mesa, then times out on my repo, before fd.o creates the pipeline in mesa/mesa. In my run just now, it took 4 re-invocations of the script before it found the MR pipeline.
On the other hand, when I'm working on a fork, non-MR pipeline, the script sits around looking in mesa/mesa even if the pipeline already exists in anholt/mesa. It wouldn't be so bad if I only had to go through it once, but I often take a few rounds trying to come up with the right job name regex.
I think the fix for both is to poll both repositories and see who comes up with the pipeline first.