Do not assume stdout/stderr are defined when spawning a child process.

[dmitrivMS]

Fixes #145505

According to child_process documentation, when the process cannot be spawned stdout/stderr will be null. Although this is probably a rare case, we should handle that case gracefully.

[vs-code-engineering]

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

@lszomoru

Matched files:

• extensions/git/src/git.ts

[Copilot]

Pull request overview

This PR adds defensive null checks for stdout and stderr streams when spawning a child process in the Git extension's getStatus method. According to Node.js child_process documentation, these streams can be null if the process fails to spawn, which could cause runtime errors when attempting to access them.

Key Changes

• Added optional chaining when removing stdout data listener during status limit handling
• Wrapped stdout listener setup in a null check to prevent errors when stream is unavailable
• Wrapped stderr listener setup in a null check to prevent errors when stream is unavailable