Added pipelines for monitoring seems to duplicate themselves

Had not seen this behaviour before, but happening since the addition of the new release pipelines, that when you add the pipeline to be monitored, at some point after its starts pulling data from the Jenkins server, it ends up showing up more than once in the monitoring admin view (even though it has not been manually added more than once).

When you try to edit or delve one of the entries from the admin view, it appears that the duplicates represent the same entries in the DB, and will get errors saying as much.

Not sure how many times a pipeline will end up showing up in this view, see that jdk8 pipeline is now 4x (and 11/17 2x), since being added yesterday, so we should figure out what is triggering this behaviour.

Start by tracing how monitored pipelines are added from the monitoring admin view to the database and how data is pulled from the Jenkins server after release pipelines run. Reproduce the repeated entries described for the jdk8 and 11/17 pipelines, then verify that one database entry remains per pipeline and that editing or deleting it no longer reports duplicate-record errors.

Written by the indexing model from the issue text.