glusterd: don't connect to an asynchronously started brick

[xhernandez]

When a brick is asynchorously started it's likely that an immediate connection attempt will fail. In this case just avoid the connection. The connection will be created the next time the brick is needed.

Fixes: #4080

[xhernandez]

/run full regression

[gluster-ant]

5 test(s) failed
./tests/bugs/glusterd/brick-mux-validation-in-cluster.t
./tests/bugs/glusterd/quorum-validation.t
./tests/bugs/glusterd/reset-brick-and-daemons-follow-quorum.t
./tests/bugs/glusterd/validating-server-quorum.t
./tests/bugs/snapshot/bug-1512451-snapshot-creation-failed-after-brick-reset.t

0 test(s) generated core

10 test(s) needed retry
./tests/000-flaky/bugs_glusterd_bug-857330/normal.t
./tests/000-flaky/bugs_glusterd_bug-857330/xml.t
./tests/basic/afr/ta-shd.t
./tests/bugs/glusterd/brick-mux-validation-in-cluster.t
./tests/bugs/glusterd/quorum-validation.t
./tests/bugs/glusterd/reset-brick-and-daemons-follow-quorum.t
./tests/bugs/glusterd/validating-server-quorum.t
./tests/bugs/quota/bug-1035576.t
./tests/bugs/replicate/bug-976800.t
./tests/bugs/snapshot/bug-1512451-snapshot-creation-failed-after-brick-reset.t

2 flaky test(s) marked as success even though they failed
./tests/000-flaky/bugs_glusterd_bug-857330/normal.t
./tests/000-flaky/bugs_glusterd_bug-857330/xml.t