Fix staggered heat call-out order and extend its shared clock

getEventDrivers followed the drivers directory's internal creation
order instead of the order participants were actually selected for
the event, so the fallback qualifying/finals grid, the Start List
display, and the staggered-release announcer all read out drivers in
a scrambled order relative to how the event was actually entered.
Fixed to preserve raceConfig.driverIds' own order.

Also, a staggered heat's shared clock/auto-finish target only ever
counted the flat session duration, not the staggered release schedule
itself - so the last-released driver's own personal window could
still be running when the session force-finished. The shared clock
now widens by (driverCount - 1) * staggerGapSec on top of the base
duration for staggered sessions; each driver's own personal quota is
unchanged.

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

src/event_race_logic.js

@@ -548,7 +548,16 @@ export function getEventDrivers(event, { state }) {
   if (!event?.raceConfig?.participantsConfigured) {
     return classDrivers;
   }
-  return classDrivers.filter((driver) => (event.raceConfig.driverIds || []).includes(driver.id));
+  // Preserves the order participants were selected in (event.raceConfig.driverIds), not
+  // the club's global driver-directory order - the two rarely match, and anything seeded
+  // from this list (a fallback qualifying/finals grid with no practice data yet, a
+  // staggered heat's start-order announcement) should follow the order a club admin
+  // actually built the entry list in, not an unrelated internal array order.
+  const classDriverIds = new Set(classDrivers.map((driver) => driver.id));
+  const byId = new Map(classDrivers.map((driver) => [driver.id, driver]));
+  return (event.raceConfig.driverIds || [])
+    .filter((id) => classDriverIds.has(id))
+    .map((id) => byId.get(id));
 }