fix(release): give the first-hop compat lane a four-hop budget (#151285)

* fix(release): give the first-hop compat lane a four-hop budget

The packaged-updater first-hop lane now proves four serial hops
(2026.9.1 through 2026.9.4). On hosted runners each hop takes about six
minutes, so the 25-minute lane budget killed the fourth hop with SIGTERM
after the first three passed (release 2026.9.5 validation run
35287969616). Size the budget like the other multi-hop update lanes.

* test(release): align first-hop lane budget expectation

scripts/lib/docker-e2e-scenarios.mts

@@ -249,7 +249,9 @@ function createPackageUpdateMaintenanceLanes() {
     npmLane("update-first-hop-compat", updateFirstHopCompatCommand, {
       resources: ["service"],
       stateScenario: "upgrade-survivor",
-      timeoutMs: 25 * 60 * 1000,
+      // Four serial packaged-updater hops (2026.9.1 through 2026.9.4) take
+      // ~6 minutes each on hosted runners; 25 minutes cut the fourth hop off.
+      timeoutMs: 45 * 60 * 1000,
       weight: 3,
     }),
     npmLane("update-run-package-self-upgrade", updateRunPackageSelfUpgradeCommand, {

test/scripts/docker-e2e-plan.test.ts

@@ -1085,7 +1085,7 @@ await import('./scripts/check-docker-e2e-boundaries.mts');`,
         name: "update-first-hop-compat",
         resources: ["docker", "npm", "service"],
         stateScenario: "upgrade-survivor",
-        timeoutMs: 1_500_000,
+        timeoutMs: 2_700_000,
         weight: 3,
       },
       {