Fix new mypy confusion about kill_after_timeout type

The refactoring in 1ef3365 before this added a new mypy error on
non-Windows platforms, where mypy failed to infer that the type of
kill_after_timeout was `float` (rather than `float | None`) at the
point in the code where it was used as a captured variable in the
newly introduced communicate() helper.

This was even though the variable is never rebound there or in the
enclosing scope that introduced it. So introducing and using a new
variable that holds the same reference, which is sufficient to fix
the problem and is the approach taken here, is not a behavioral
change.

Author: EliahKagan

Diff for: git/cmd.py

@@ -1180,6 +1180,8 @@ def execute(
             return self.AutoInterrupt(proc, command)
 
         if sys.platform != "win32" and kill_after_timeout is not None:
+            # Help mypy figure out this is not None even when used inside communicate().
+            timeout = kill_after_timeout
 
             def kill_process(pid: int) -> None:
                 """Callback to kill a process.
@@ -1216,7 +1218,7 @@ def communicate() -> Tuple[AnyStr, AnyStr]:
                 if kill_check.is_set():
                     err = 'Timeout: the command "%s" did not complete in %d ' "secs." % (
                         " ".join(redacted_command),
-                        kill_after_timeout,
+                        timeout,
                     )
                     if not universal_newlines:
                         err = err.encode(defenc)
@@ -1225,7 +1227,7 @@ def communicate() -> Tuple[AnyStr, AnyStr]:
             # END helpers
 
             kill_check = threading.Event()
-            watchdog = threading.Timer(kill_after_timeout, kill_process, args=(proc.pid,))
+            watchdog = threading.Timer(timeout, kill_process, args=(proc.pid,))
         else:
             communicate = proc.communicate