[MINOR][CI] Reduce surefire per-fork test timeout from 1380s to 600s

[Baunsgaard]

The per-fork timeout existed to kill a hung test fork before the 30 min CI cap, so the offending test is named in the log instead of GitHub cancelling the whole job. At 1380s the timeout fired ~23 min after a fork started, but earlier forks already consumed ~8 min of the run, so the timeout would only trigger after the 30 min cap had cancelled the job. As a result hung forks were never reported.

Lowering to 600s keeps a large margin below the cap regardless of when in the run a fork hangs, while staying well above the slowest observed test class (~35s), so legitimate tests are not killed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.39%. Comparing base (ae9a59c) to head (030086f).

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2485      +/-   ##
============================================
- Coverage     71.41%   71.39%   -0.03%     
- Complexity    48774    48776       +2     
============================================
  Files          1571     1571              
  Lines        188912   188912              
  Branches      37067    37067              
============================================
- Hits         134917   134868      -49     
- Misses        43544    43587      +43     
- Partials      10451    10457       +6     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.