chore: requires user to pass context to propagation APIs

[Flarna]

Which problem is this PR solving?

At least for extract() using the current active context is often a bad choice because usually a plugin wants to use an extracted span instead the current active.

Short description of the changes

Change propagation APIs to require context as first argument instead of using active context on default. This ensures that plugin developers have to be explicit instead of relying on a potential wrong default.

This PR is an enhanced but API breaking variant of #1714.

[vmarchaud]

lgtm

[codecov]

Codecov Report

Merging #1734 (0e2db5f) into master (0d06a52) will increase coverage by 0.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1734      +/-   ##
==========================================
+ Coverage   91.96%   92.17%   +0.20%     
==========================================
  Files         167      167              
  Lines        5599     5594       -5     
  Branches     1193     1191       -2     
==========================================
+ Hits         5149     5156       +7     
+ Misses        450      438      -12     

Impacted Files	Coverage Δ
...telemetry-plugin-grpc-js/src/server/patchServer.ts	88.52% <ø> (ø)
packages/opentelemetry-api/src/api/propagation.ts	92.85% <100.00%> (+36.60%)	⬆️
...ges/opentelemetry-instrumentation-http/src/http.ts	95.49% <100.00%> (ø)
...emetry-instrumentation-xml-http-request/src/xhr.ts	96.77% <100.00%> (ø)
packages/opentelemetry-plugin-fetch/src/fetch.ts	96.52% <100.00%> (-0.03%)	⬇️
...s/opentelemetry-plugin-grpc-js/src/client/utils.ts	93.25% <100.00%> (ø)
packages/opentelemetry-plugin-grpc/src/grpc.ts	93.26% <100.00%> (ø)
packages/opentelemetry-plugin-http/src/http.ts	97.28% <100.00%> (ø)
...ackages/opentelemetry-shim-opentracing/src/shim.ts	87.70% <100.00%> (ø)

[obecny]

@Flarna pls allow edits or update the branch

[Flarna]

@obecny I enabled it on my PR but as far as I know github doesn't support/allow edits for org repos like that one I have to use because of company rules.

[Flarna]

Failed test seems to be unrelated.

   1) Packages
       get
         should create a span for GET requests and add propagation headers by using got package:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/__w/opentelemetry-js/opentelemetry-js/packages/opentelemetry-plugin-http/test/functionals/http-package.test.ts)
      at listOnTimeout (internal/timers.js:554:17)
      at processTimers (internal/timers.js:497:7)

[obecny]

Failed test seems to be unrelated.

   1) Packages
       get
         should create a span for GET requests and add propagation headers by using got package:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/__w/opentelemetry-js/opentelemetry-js/packages/opentelemetry-plugin-http/test/functionals/http-package.test.ts)
      at listOnTimeout (internal/timers.js:554:17)
      at processTimers (internal/timers.js:497:7)

It is failing in few other places. It is http plugin test, @vmarchaud you are the most familiar with this plugin, do you have maybe idea what can be the issue ? for example here too https://github.com/open-telemetry/opentelemetry-js/pull/1687/checks?check_run_id=1550385379

[vmarchaud]

It is failing in few other places. It is http plugin test, @vmarchaud you are the most familiar with this plugin, do you have maybe idea what can be the issue ? for example here too https://github.com/open-telemetry/opentelemetry-js/pull/1687/checks?check_run_id=1550385379

I didn't wrote that part but from the comment its seems that got is cannot be mocked so we tries to reach http://info.cern.ch which is currenly down.
I think its safe to merge this and tries to fix the got problem in a seperate PR, WDYT ?

[obecny]

It is failing in few other places. It is http plugin test, @vmarchaud you are the most familiar with this plugin, do you have maybe idea what can be the issue ? for example here too https://github.com/open-telemetry/opentelemetry-js/pull/1687/checks?check_run_id=1550385379

I didn't wrote that part but from the comment its seems that got is cannot be mocked so we tries to reach http://info.cern.ch which is currenly down.
I think its safe to merge this and tries to fix the got problem in a seperate PR, WDYT ?

Yea it makes sense, now I see this external domain, thx @vmarchaud for explanation