fix(ci): deduplicate check runs in all-green script to handle re-runs (#7719)

When a check is re-run (e.g. after adding a missing semver label), GitHub
keeps the old failed check run alongside the new successful one. The
all-green script was scanning all historical runs and failing on the
stale failures. Fix by grouping runs by name and evaluating only the
latest run for each check, making the summary table consistent with
the pass/fail decision.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: bm1549

scripts/all-green.mjs

@@ -69,23 +69,34 @@ async function checkCompleted () {
 }
 
 async function checkAllGreen () {
-  let checkRuns
+  let latestRuns
 
   try {
     await checkCompleted()
   } finally {
-    checkRuns = await octokit.paginate(
+    const checkRuns = await octokit.paginate(
       'GET /repos/:owner/:repo/commits/:ref/check-runs',
       {
         ...params,
         per_page: 100,
       }
     )
 
-    printSummary(checkRuns)
+    // When a check is re-run, older runs remain with their original conclusions.
+    // Deduplicate by name and evaluate only the latest run for each check.
+    const latestByName = new Map()
+    for (const run of checkRuns) {
+      const existing = latestByName.get(run.name)
+      if (!existing || new Date(run.started_at) >= new Date(existing.started_at)) {
+        latestByName.set(run.name, run)
+      }
+    }
+    latestRuns = [...latestByName.values()]
+
+    printSummary(latestRuns)
   }
 
-  const allGreen = !checkRuns.some(run => (
+  const allGreen = !latestRuns.some(run => (
     run.conclusion === 'failure' || run.conclusion === 'timed_out'
   ))