Can't get profiling data from non-osprofiler service.

[Shoham Peller]

I have a non-osprofiler service which reports profiling data to Jaeger. The service uses openstack clients to call openstack services. The openstack clients use osprofiler to get the currently used span id and trace id. But osprofiler gets that data from it's own profiler object in the TLS memory, and sees that there's no current span. The service stored the IDs in jaeger-client's memory.

We want non-osprofiler services to work seamlessly with osprofiler services, so we need to add other methods for openstack clients to get the currently used span IDs and trace IDs. Not only from osprofiler's profiler, since that is not configured in the non-osprofiler service, but also from other resources. Such resources may be jaeger-client's current trace/span IDs.