OpenTracing duplicates user created spans during replay

Expected Behavior

If we have the following code somewhere in workflow:

void execute() {
  ...
  withSpan(() -> {
    activity.runActivity();
  })
  ...
  //end of replay somewhere down from the above code block
}

If we replay the code above, we should ignore the span creation, because this span was already reported during the original execution.

Actual Behavior

The second span will be created during replay.

Proposed solution

We should create a thin layer on top of Tracer, ScopeManager, Scope or Span that will check if we are still replaying on span finalization and if we are - discard the span instead of finalizing it.

Notes

The issue is raised here:
#951
https://github.com/temporalio/sdk-java/pull/951#pullrequestreview-844189585

And the solution is originally proposed here:
https://github.com/temporalio/sdk-java/pull/951#issuecomment-1005896960

Start with the withSpan example and the proposed Tracer, ScopeManager, Scope, and Span layer, then read issue #951 and its linked pull-request review and comment. Trace span finalization during workflow replay; done means spans created during replay are discarded instead of finalized.