TestResourceTracker not working properly for OSGi tests

The OSGi tests are running in a different process from the test driver and are executed through RMI. The assumptions that the test name is contained in the thread name and that there's a one-to-one mapping from thread to test is no longer valid (ThreadLocal used for the test name).

Executing the tests in integrationtests/osgi will result in many log messages similar to this one:

Test name not set in unknown thread RMI TCP Connection(3)-127.0.0.1