This is an exact duplicate of what we saw in T129517: refreshLink jobs that are recursive keep feeding the queue with more and more jobs, and the jobrunners are processing them at unprecedented rates.
While it isn't very refreshing (pun intended) to see that ONE YEAR LATER no one bothered to look into the original bug, I think we can assume re-doing what @ori did last year is safe, and I will just do it.