don't crash connection pool when handling done from unknown pid
don't crash connection pool when handling done from unknown pid

There's a tiny chance for connection pool to receive EXIT message and
die when xdcr is having frequent crashes (i.e. during
rebalance). That's relatively normal.

What is not normal is that newly started connection pool instance
would crash again when socket is returned back to it from unknown
process.

In order to fix it we now simply drop such requests (and sockets) on
the floor.

Change-Id: I5cfe87c88f8f7b497eb9c89e9846b0fb871c3b94
Reviewed-on: http://review.couchbase.org/35530
Tested-by: Aliaksey Kandratsenka <340b8e09ca65cd3fc686427fcfed17e87eaf61e2@gmail.com>
Reviewed-by: Artem Stemkovski <15a0730a27c69f62ab86f2b6c639fca202166c02@couchbase.com>

nimishzynga/ns_server,t3rm1n4l/ns_server,daverigby/ns_server,nimishzynga/ns_server,daverigby/ns_server,mschoch/ns_server,mschoch/ns_server,ceejatec/ns_server,t3rm1n4l/ns_server,ceejatec/ns_server,membase/ns_server,nimishzynga/ns_server,nimishzynga/ns_server,membase/ns_server,t3rm1n4l/ns_server,ceejatec/ns_server,daverigby/ns_server,membase/ns_server,mschoch/ns_server,ceejatec/ns_server,t3rm1n4l/ns_server,ceejatec/ns_server,ceejatec/ns_server,mschoch/ns_server,mschoch/ns_server,membase/ns_server,t3rm1n4l/ns_server,mschoch/ns_server,nimishzynga/ns_server,membase/ns_server,daverigby/ns_server,nimishzynga/ns_server,membase/ns_server,daverigby/ns_server