use dedicated scheduler thread pool for discovery

Currently discovery uses the commons.scheduler for a few but mission critical cases. Since the commons.scheduler doesn't guarantee timely execution - eg when the corresponding thread pool is full - discovery should become independent of commons.scheduler.

The easiest solution is to spawn new Thread in those few cases. This shouldn't be problematic since these activities are not happening on a high frequency and are only short-lived.