util: remove the obsolete non-blocking connect

util: remove the obsolete non-blocking connect

The non-blocking connect mechanism is obsolete, and it doesn't
work well in inet connection, because it will call getaddrinfo
first and getaddrinfo will blocks on DNS lookups. Since commit
e65c67e4 & d984464e, the non-blocking connect of migration goes
through QIOChannel in a different manner(using a thread), and
nobody use this old non-blocking connect anymore.

Any newly written code which needs a non-blocking connect should
use the QIOChannel code, so we can drop NonBlockingConnectHandler
as a concept entirely.

Suggested-by: Daniel P. Berrange <[email protected]>
Signed-off-by: Cao jin <[email protected]>
Signed-off-by: Mao Zhongyi <[email protected]>
Reviewed-by: Juan Quintela <[email protected]>
Signed-off-by: Daniel P. Berrange <[email protected]>