Drop stale CREATE_BREAKAWAY_FROM_JOB comment

The header comment was left over from an earlier iteration that
tried to detach the grandchild via CREATE_BREAKAWAY_FROM_JOB. The
script only passes CREATE_NO_WINDOW (0x08000000); what actually
makes Kill(true) miss the grandchild is the PPID chain breaking
when cmd exits after `start /b` returns. The comment lower down
already describes this correctly, so drop the stale header.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: LukeButters

source/Octopus.Tentacle.Tests.Integration/Util/SilentProcessRunnerFixture.cs

@@ -125,17 +125,7 @@ public void CancellationToken_ShouldForceKillTheProcess()
         [WindowsTest]
         public async Task CancellationToken_WhenGrandchildHoldsRedirectedPipes_ShouldNotHang()
         {
-            // Reproduces a dump scenario: a child process spawns a grandchild that
-            // inherits the redirected stdout/stderr handles AND is detached from the
-            // .NET-managed job (CREATE_BREAKAWAY_FROM_JOB). When cancellation fires:
-            //   - Hitman.Kill terminates the immediate child.
-            //   - The grandchild survives and keeps the write-end of the pipes open.
-            //   - Process.WaitForExit() blocks forever waiting for the readers to EOF.
-            // The fix is to close StandardOutput/StandardError after Kill so the
-            // readers see EOF on our end and WaitForExit returns.
-
             var grandchildPidFile = Path.Combine(Path.GetTempPath(), $"silent-runner-grandchild-{Guid.NewGuid():N}.pid");
-
             var diagnosticsFile = grandchildPidFile + ".log";
 
             // Reproduces the dump pattern (PowerShell -> AutoReport -> AutoReport-child):