Failed provisioning attempts sometimes do not show up in agent history

I tried deploying ancientminister with Ubuntu 26.04 today via Testflinger. This attempt failed because of [a known bug in MAAS](https://bugs.launchpad.net/maas-images/+bug/2151116). (I'd been testing to see if the fix has been deployed yet; it hadn't been.) The Testflinger issue is that the [ancientminister provisioning history](https://testflinger.canonical.com/agents/ancientminister) in the Testflinger web UI doesn't show any hint of the failure. When searching on the job ID ([25a67bf1-0545-42d2-8ded-f4aa1976dcc5](https://testflinger.canonical.com/jobs/25a67bf1-0545-42d2-8ded-f4aa1976dcc5)), the failure does show up correctly, but it is somehow not linked to the agent's provisioning list in the web UI.

Reproduce the issue using job 25a67bf1-0545-42d2-8ded-f4aa1976dcc5, then compare its job-search result with the ancientminister provisioning history in the Testflinger web UI. Trace how failed provisioning jobs are associated with an agent's history. Done means the failed attempt appears in the agent history while remaining visible through job search.

Written by the indexing model from the issue text.