[Jaeger Tracing] Undesired Tracing Span Graph in NCM

[zzxgzgz]

What happend:

• With Jaeger Tracing added to the NCM in this PR, we found that the tracing graphs is not what we wanted, please refer to the graph below:
  
  the alcor.schema.GoalStateProvisioner/RequestGoalStates spans should be at the same level, rather than one being the child of the previous one.

We suspect that it has to do with this issue, we should try to implement the solution proposed in this issue as a solution. Another solution we can think of is replaceing the opentracing libraries with the opentelemetry libraries, the detail of which can be found in this issue