Using lazygit on windows crashes and wrecks terminal input/output

### Describe the bug
Lazygit on windows crashes and leaves the terminal in an unusable state. It stops reacting properly to input and output is single line and laced with escape characters.

### To Reproduce
Steps to reproduce the behavior:

Open lazygit in a folder with a remote set, using ssh-git url, keybased auth, and no key in ssh-agent.
Lazygit opens, but crashes when it tries to do anything

### Expected behavior
It should not crash...

### Screenshots
[IMGUR video gif of behavior](https://i.imgur.com/rVu5Nsc.gif)

### Version info:

commit=2f6d20275afd5fc9b623500c9194a2c732936014, build date=2026-03-09T19:51:31Z, build source=binaryRelease, version=0.60.0, os=windows, arch=amd64, git version=2.53.0.vfs.0.0

### Terminal info:
Windows Terminal 1.23.20211.0

### Additional context
Log output
```
Mar 16 13:26:55 |DEBU| RunCommand command="git --version"
Mar 16 13:26:56 |INFO| git --version (111.0735ms)
Mar 16 13:26:56 |DEBU| RunCommand command="git -C C:\\Code\\adventofslack rev-parse --path-format=absolute --show-toplevel --absolute-git-dir --git-common-dir --is-bare-repository --show-superproject-working-tree"
Mar 16 13:26:56 |ERRO| command="git rev-parse --verify --quiet refs/heads/master"
Mar 16 13:26:56 |INFO| git rev-parse --verify --quiet refs/heads/master (103.0282ms)
Mar 16 13:26:56 |DEBU| RunCommand command="git rev-list HEAD ^refs/remotes/origin/main"
Mar 16 13:26:56 |DEBU| RunCommand command="git rev-list refs/heads/main ^main@{u} ^refs/remotes/origin/main"
Mar 16 13:26:57 |INFO| git rev-list HEAD ^refs/remotes/origin/main (117.697ms)
Mar 16 13:26:57 |INFO| git rev-list refs/heads/main ^main@{u} ^refs/remotes/origin/main (117.7445ms)
Mar 16 13:26:57 |DEBU| using cache for key rebase.updateRefs
Mar 16 13:26:57 |INFO| postRefreshUpdate for commits took 708µs
Mar 16 13:26:57 |DEBU| using cache for key rebase.updateRefs
Mar 16 13:26:57 |DEBU| using cache for key rebase.updateRefs
```

I don't see anything related to the crash in the logs, but the behavior makes me think that something crashes in the TUI-library, and not in lazygit itself. Or something in the communication between lazygit and the TUI library...