[#1962] Wrap returned promises in OpenTracingOutboundCallsInterceptor

[ghaskins]

This change allows the OpenTracing interceptor to transfer any active trace/span from
the point of invocation to the point of promise callback execution, thus preserving
the span within the callback.

Without this, spans become disjoint across Promise.thenCompose, due
to the nature of the deferring the execution of the .thenCompose to a callback thread.

Fixes #1962

Checklist

1. Closes Tracing context does not propagate into .thenCompose #1962

2. How was this tested:
   A unit test was developed first to confirm the issue. The solution was iterated over until the unit test passed satisfactorily. The unit-test is included in the MR for inclusion with the code-base

3. Any docs updates needed?
   No.

[cretz]

Hrmm, this is a very specific interceptor-oriented solution to a general problem of contextual state across promises. I wonder if a WorkflowAsyncLocal is best which behaves like thread local, but also propagates across promises. This is the common solution to this problem in other languages, make a way to propagate state across async (Go is context, Python is contextvars, .NET is AsyncLocal, etc).

[ghaskins]

@cretz, if I understand what you are saying, I think we'd still need to use interception at some level unless OTEL can be made to utilize the WorkflowAsyncLocal instead of ThreadLocal because something would need to initialize the state in the callback context, which currently runs outside of the RootThread complex. I'm not saying OTEL can't use WorkflowAsyncLocal; I just don't know

[Quinn-With-Two-Ns]

@ghaskins Looks like part of CI is failing because your branch is missing the version tags, can you make sure you fetched tags when fetched? I will try to prioritize adding a fallback in our CI but for now the quickest would be just to push make sure tags are present.

[Quinn-With-Two-Ns]

There are a lot of futures in the interceptor that are not wrapped, I will need to go and wrap them, that is one big drawback with this approach, but given the other constraints I can't think of a better approach.

[ghaskins]

@Quinn-With-Two-Ns pushed tags