Fixed exception handling for Windows (using ProxyCommand in native ss…

[phr34k]

On windows when you use native-ssh and "ProxyCommand" it uses pipes to read stdin/stdout. The exception handling doesn't handle EWOULDBLOCK, so you get an following error like "A non-blocking socket operation could not be completed immediately. - read would block". This change prevents that.

(1) > bolt command run whoami -t support@somewhere --no-host-key-check  --native-ssh
CLI arguments ["host-key-check", "native-ssh"] might be overridden by Inventory: D:/bolt/inventory.yaml [ID: cli_overrides]
Started on support@somewhere...
Failed on support@somewhere:
  A non-blocking socket operation could not be completed immediately. - read would block
Failed on 1 target: support@somewhere
Ran on 1 target in 23.22 sec

[CLAassistant]

All committers have signed the CLA.