The Notification Listener Tracker class is not threadsafe,
so when a test stop an already stopped listener this one
can be restarted, due to concurrency access of the threads list and
concurrency execution of the start/stop/wait method of the notification
listener.
This result of a lockup of the test or a listener can continue to
got unepxected message.
This change fixes that by never stop the tread with the tracker callback
but only manually with the test.
This test also rename some 'Listener' to 'Server', to not mismatch
the driver listener from the notification listener.
Closes-bug: #1410902
Change-Id: I4777c7dd0ba71c61850d36641e85f33f9461e9c1