LabVIEW CI 4.17.0

Fixed the dashboard's disappearing "Queued" pills. When a queued run died before it could report anything — typically the repository ran out of GitHub Actions minutes, hit a billing block, or the run was cancelled while still waiting for a runner — the dashboard lost all trace of it: the browser's optimistic Queued badge silently expired about 20 minutes after you queued, and the rebuilt page showed a clean idle cell, as if nothing had ever been queued. Dead runs now stay visible everywhere: the badge in the queuing browser turns into a sticky red Failed marker within a minute even when the run dies in seconds, and the dashboard itself now renders a red Failed badge — for every viewer — on any cell whose latest run ended without reporting a result, linking straight to the dead run so the cause is one click away. The badge yields to any newer result, ages out after a day, and Populate history counts those cells as missing so Fill re-queues them. Warm-container batch backfills are covered too: the single batch run is now tracked per revision both in the browser and on the rebuilt page (its run name carries the revision list), so a healthy batch no longer watches its badges evaporate mid-run. The history card's concurrency note now describes how queued runs actually pace themselves (GitHub's account-wide runner limit) instead of a per-repository cap that was never enforced.

Consumers pinned at the major alias (e.g. @v4) receive this automatically.