Fixes a panic related to noop embeded span context in ddtrace/opentelemetry

[dianashevchenko]

Description

Related to DataDog/dd-trace-go#2284
Embedding a noop.Span caused a panic when casting a span to ddtrace.Span

Motivation

Workflow

1. ⚠️⚠️ Create your PR as draft
2. Follow the style guidelines of this project (See how to easily lint the code)
3. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
4. Mark it as ready for review

Once your PR is reviewed, you can merge it! ❤️

Reviewer checklist

• Check what scenarios are modified. If needed, add the relevant label (run-parametric-scenario, run-profiling-scenario...). If this PR modifies any system-tests internal, then add the run-all-scenarios label (more info).
• CI is green
  • If not, failing jobs are not related to this change (and you are 100% sure about this statement)
• if any of build-some-image label is present
  1. is the image labl have been updated ?
  2. just before merging, locally build and push the image to hub.docker.com
• if a scenario is added (or removed), add (or remove) it in system-test-dasboard nightly

[katiehockman]

/merge

[dd-devflow]

🚂 MergeQueue

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

you can cancel this operation by commenting your pull request with /merge -c!

[katiehockman]

/remove

[dd-devflow]

🚂 Devflow: remove

[dd-devflow]

⚠️ MergeQueue

This merge request was unqueued

If you need support, contact us on slack #ci-interfaces!