ubuntu-base images propagated to the isotracker for multiple unrelated milestones

[Łukasz Zemczak]

I don't have a full understanding of the issues here, but I observed this twice already. Situation: when working on Noble Final, we spun ubuntu-base images on the 20240422.1 datestamp - since then there was no rebuilds of these images. On release day, we noticed that isotracker lists 202404025 images in the Noble Final milestone. Looking closer, it looks like there was a 20240425 jammy build of ubuntu-base. My suspicion is that something is not right on the line between cdimage -> isotracker, either in the tracker itself *or* the Python bindings, causing the post_qa call to update more than just the related per-series milestones.