feat: add startActiveSpan method to Tracer

[naseemkullah]

Which problem is this PR solving?

• fixes [Tracer] implement startActiveSpan() #2210
• also adds reset script in root package.json that comes in handy when linting rules differ between local and CI

Short description of the changes

• implements startActiveSpan as defined in the trace API

[codecov]

Codecov Report

Merging #2221 (d5bab9b) into main (d551781) will increase coverage by 0.41%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##             main    #2221      +/-   ##
==========================================
+ Coverage   92.29%   92.71%   +0.41%     
==========================================
  Files         144      144              
  Lines        5168     5160       -8     
  Branches     1064     1056       -8     
==========================================
+ Hits         4770     4784      +14     
+ Misses        398      376      -22     

Impacted Files	Coverage Δ
packages/opentelemetry-tracing/src/Tracer.ts	98.38% <93.33%> (+31.24%)	⬆️

[dyladan]

This should fix your overload issues i think

[vmarchaud]

i think it makes sense to add test in both the node sdk (which bundle the async hooks context manager) and the web (with the zone context manager)

[obecny]

I did so far all necessary refactoring for the core repo with regards to api 0.20 just waiting for it to be released. I took exactly the same implementation that exists already in api for this function. Maybe I'm missing something but why it cannot be the same ?, your ts doc is much cooler than mine though :D. So curious why it needs to be different ?

[naseemkullah]

I did so far all necessary refactoring for the core repo with regards to api 0.20 just waiting for it to be released. I took exactly the same implementation that exists already in api for this function. Maybe I'm missing something but why it cannot be the same ?, your ts doc is much cooler than mine though :D. So curious why it needs to be different ?

Oh good point, I guess you. mean the implementation in noop tracer? Thats what I copy pasted originally here but @dyladan pointed out the preference for function overloads which I agree with, just could not get right in the api PR for the noop tracer implementation.

As for the ts doc its the one I put in the tracer interface :)

With that said, I think this implementation is better and can make a PR to api repo to overwrite the noop tracer implementation, wdyt?

[naseemkullah]

open-telemetry/opentelemetry-js-api#81 created to make implementation same

[dyladan]

Looks great thanks

[naseemkullah]

Looks great thanks

Np, thanks for the help!

[obecny]

lgtm