Nuclide does not integrate well with system SSH

[syakhmi]

Issue and Steps to Reproduce

In strict environments, like some corporate environments, the only way to establish a remote connection may be the system ssh. Because nuclide tries to handle ssh internally using a pure javascript library, it simply does not work in these environments.

For example, Nuclide does not appear to respect the ssh Host configuration (like ProxyCommand or ControlMaster) that would make the connection possible.

Expected Behavior

Nuclide should allow making a remote connection using the system ssh, either by allowing the user to establish the tunnel outside of Nuclide (forwarding the appropriate ports), or by re-using the system ssh implementation to make the connection.

Actual Behavior

Nuclide fails to establish a connection in one of several ways -- failure to authenticate, failure to resolve hostname (if proxy is required), etc.

Versions

• Atom: 1.10.0
• Nuclide: 0.166.0
• Client OS: OS X El Capitan 10.11.6
• Server OS (optional):

Additional Details

• Installed packages (apm ls --installed):

[jjh42]

This is very related to #282