fix: add windows ssh agent pipe fallback for ssh conns

[janburzinski]

Summary

• add a shared ssh agent socket resolver that fallsback to the Windows openssh named pipe when SSH_AUTH_SOCK is unavailable
• usethat fallback for agent auth and agent forwarding in SSH connection setup

[greptile-apps]

Greptile Summary

This PR adds a Windows fallback for SSH agent sockets. The main changes are:

• A shared SSH agent socket resolver.
• A Windows OpenSSH named-pipe fallback when SSH_AUTH_SOCK is missing.
• Use of the shared resolver for agent auth and agent forwarding.
• A forwarded platform dependency for production and test SSH connection config.
• Tests for Windows fallback behavior and disabled-agent forwarding cases.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
apps/emdash-desktop/src/main/core/ssh/connect/ssh-connect-forward-agent.ts	Moves the disabled-agent check before explicit forwarding values and uses the shared fallback resolver.
apps/emdash-desktop/src/main/core/ssh/connect/ssh-connect-auth.ts	Uses the shared default agent socket resolver for agent authentication.
apps/emdash-desktop/src/main/core/ssh/connect/ssh-agent-socket.ts	Adds the shared default SSH agent socket helper and Windows OpenSSH pipe constant.
apps/emdash-desktop/src/main/core/ssh/connect/resolve-ssh-connect-config.ts	Adds platform to SSH connection dependencies.
apps/emdash-desktop/src/main/core/ssh/connect/production-connect-config.ts	Passes process.platform into the production SSH connection resolver.
apps/emdash-desktop/src/main/core/ssh/connect/resolve-ssh-connect-config.test.ts	Adds coverage for Windows fallback behavior and disabled-agent forwarding behavior.

_{Reviews (3): Last reviewed commit: "fix(ssh): block explicit forwarding when..." | Re-trigger Greptile}

[janburzinski]

@greptileai

[janburzinski]

@greptileai