test(ship-budget): give the GSTA-152 PR B replay an explicit 120s timeout

It spawns about 100 CLI processes; on windows-latest it ran past the
shard runner's 30s per-test timeout (windows-free-shard 5, run
40917695070), and on 2 cores it sat at bare bun test's 5s default.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

test/ship-budget-projection.test.ts

@@ -113,7 +113,7 @@ describe('projection calibrated from the run\'s own meter (GST-101)', () => {
     }
     expect(stop).toContain('STOP: reason=budget_exhausted');
     expect(reading + STOP_26).toBeLessThanOrEqual(cap);
-  });
+  }, 120_000);
 
   test('the prior holds until the first measurement; the tail reserve scales with the measured step cost', () => {
     const h = fresh();