Batch-mode Editor does not exit after the heartbeat timeout when a Standalone Play Mode test player is forcefully terminated

Steps to reproduce:

1. Open the attached “IN-153057” project
2. Wait for the project to finish importing and compiling
3. Close the Unity Editor and ensure no other Unity instance has the project open
4. Open PowerShell and set the paths to the Unity executable and project:
   $UnityPath = "<full-path-to-Unity.exe>"
   $ProjectPath = "<full-path-to-IN-153057-project>"
5. Delete files from previous test runs:
   Remove-Item "$ProjectPath\results.xml" -Force -ErrorAction SilentlyContinue
   Remove-Item "$ProjectPath\editor-run.log" -Force -ErrorAction SilentlyContinue
6. Run the Standalone Play Mode tests without adding -quit:
   & $UnityPath `
   -batchmode `
   -projectPath $ProjectPath `
   -runTests `
   -testPlatform StandaloneWindows64 `
   -testResults "$ProjectPath\results.xml" `
   -playerHeartbeatTimeout 60 `
   -logFile "$ProjectPath\editor-run.log"
7. Open another PowerShell tab and monitor the Editor log:
   $ProjectPath = "<full-path-to-IN-153057-project>"
   while (-not (Test-Path "$ProjectPath\editor-run.log")) {
   {{ Start-Sleep -Seconds 1}}
   }
   Get-Content "$ProjectPath\editor-run.log" -Wait
8. Wait until the Standalone test player launches and the log contains: “Platform: WindowsPlayer”
9. Open another PowerShell tab and forcefully terminate the test player:
   taskkill /F /IM PlayerWithTests.exe
10. Wait until the Editor log contains: Test execution timed out. No activity received from the player in 60 seconds
11. Wait another 5–15 minutes
12. In another PowerShell tab, check whether the batch-mode Unity process is still running and whether the results file was created:
    $ProjectPath = "<full-path-to-IN-153057-project>"
    Get-CimInstance Win32_Process -Filter "Name='Unity.exe'" |
    {{ Where-Object {}}
    {{ $_.CommandLine -like "$ProjectPath" -and}}
    {{ $_.CommandLine -like "-runTests"}}
    {{ } |}}
    {{ Select-Object ProcessId, CommandLine}}
    Test-Path "$ProjectPath\results.xml"
13. Observe the result:

Actual result: The timeout is logged, but the test run does not complete. The batch-mode Unity.exe process remains running, results.xml is not created, and no test-completion or exit message is logged
Expected result: The timed-out test run is reported as failed, the test results are saved, and the batch-mode Unity.exe process exits with code 3

Reproducible with: 6000.0.0f1, 6000.0.84f1, 6000.3.24f1, 6000.6.1f1, 6000.7.0a6

Reproducible on: Windows 11
Not reproducible on: No other environments tested