Fix registry badge showing pass despite a partial/failed cycle

fillRegistrySummary derived LastResult from whichever single checks row
happened to have the latest checked_at, not the cycle's actual aggregated
result — a cycle with a mix of passing and failing checks (e.g. one egress
target timed out while the rest, including the chronologically-last check,
succeeded) rendered as a green "pass" badge on /registry, disagreeing with
the correct "partial" badge already shown on /ips for the same address.

Now prefers ip_queue.overall_result (the orchestrator's own aggregation)
when a live queue row has a finished cycle, leaves the badge blank while a
cycle is still in progress, and only falls back to classifying the most
recent cycle's own checks (pass/fail/partial) once the address has been
deleted from the queue and overall_result is no longer available.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

bin/SHA256SUMS

@@ -1,4 +1,4 @@
-62fb7e4e6a05f60e0e2f1d113c11b4ef46840eadb87202c3539a508ea0e996ae  control-api
-7c11ffe00f09cbfc33bab57d8a889cdfedacc69f0049a5881705dfabc154fa76  validator-agent
-543f7df07939d576b79dc8fdc655ee6ff5577c834d5606a1e99687b99d2a8927  prober
-2e9798e86ebaf92e70622cbd76ca0d3de8f90958eadbe7c71fb2118940b4a275  admin-dashboard
+d3559945184a9716fc1dae0defbd008b23352f8695ad9b96174838523da9c30d  control-api
+bad182f50f6ec38cb767bd275d91497298188258306a81178547b80a81fcbfe3  validator-agent
+383858b838e2707b7eae271e5023f9a28806ff8b34b3f88b40e27eb9e4eb8128  prober
+8f5ebc9983dd1aa3cdff212e6d7b17406e49fdd2de7364ae1833a0a5629f0217  admin-dashboard