MB-8378 Clean up all the TAP connections within a destroy thread
MB-8378 Clean up all the TAP connections within a destroy thread

As a separate dedicated thread performs destroying an engine
instance, we can simply clean up all the TAP connections within
that destroy thread. In this way, it doesn't need to wait for
NON-IO dispather to complete cleaning up TAP connections.

Change-Id: I39f3373b2867a2357a4f802bdc4e6ba77f4f5c82
Reviewed-on: http://review.couchbase.org/26625
Reviewed-by: Michael Wiederhold <a17fed27eaa842282862ff7c1b9c8395a26ac320@couchbase.com>
Tested-by: Chiyoung Seo <8b279095f11c26cc21045fda5a3e51debb005aa9@gmail.com>

hisundar/ep-engine,hisundar/ep-engine,daverigby/ep-engine,owendCB/ep-engine,jimwwalker/ep-engine,couchbase/ep-engine,daverigby/kv_engine,sriganes/ep-engine,membase/ep-engine,daverigby/kv_engine,hisundar/ep-engine,owendCB/ep-engine,teligent-ru/ep-engine,jimwwalker/ep-engine,daverigby/kv_engine,membase/ep-engine,membase/ep-engine,hisundar/ep-engine,owendCB/ep-engine,teligent-ru/ep-engine,sriganes/ep-engine,teligent-ru/ep-engine,membase/ep-engine,couchbase/ep-engine,teligent-ru/ep-engine,couchbase/ep-engine,daverigby/ep-engine,daverigby/ep-engine,sriganes/ep-engine,daverigby/ep-engine,jimwwalker/ep-engine,couchbase/ep-engine,jimwwalker/ep-engine,owendCB/ep-engine,daverigby/kv_engine,sriganes/ep-engine