fix(cli-framework/utils): catch connected socket.

[rdlabo]

when don't get sock.on('connect') Event, if (sock.connecting === true) get connected status.
It worked well in my environment.

Fixes #3410

[imhoffd]

But sock.connecting is set to true whenever sock.connect() is called (https://nodejs.org/api/net.html#net_socket_connecting). This is the same as not attempting connections at all, isn't it?

[imhoffd]

This can lead to the ERR_CONNECTION_REFUSED error in Chrome because the HTTP server isn't accepting connections. I believe @amanitequeen ran into this when testing: #3410 (comment)

[rdlabo]

@dwieeb thanks for review. and as you pointed out, I confirm sock.connecting is set to true whenever error connect.

I make another pull request. It worked well in my environment(localhost). Please review this pull request.
#3444