[sdk-trace-base] add debug-level log with stack trace when modifying neded span

[pichlermarc]

Description

Since the requirement for the OTel API is to not throw when invalid operations are performed, we log a warning instead when an operation on an already ended span will have no effect. However, because usually there's no stack trace attached to it, it is difficult to chase down where these invalid operations are happening.

The goal of this issue is to add a debug-level log right after the warn-level log that also provides a stack trace.

This issue is considered done when:

• A debug-level log has been added that provides a stack trace
• The warn-level log message has been amended to mention that changing the level to debug will provide the stack trace
• Tests have been added in this file (adding it here will ensure that both Node.js and Browser cases are tested)

Additional Requirements

• Since this is sdk-trace-base, the chosen approach MUST work for both Node.js and Browser

Additional Info and Links

• This is where we log the warning:

  opentelemetry-js/packages/opentelemetry-sdk-trace-base/src/Span.ts

  Line 367 in eb3ca4f

  `Can not execute the operation on ended Span {traceId: ${this._spanContext.traceId}, spanId: ${this._spanContext.spanId}}`

• Span test file https://github.com/open-telemetry/opentelemetry-js/blob/8900cfdbbab27f464df569a4c8309b96594c276b/packages/opentelemetry-sdk-trace-base/test/common/Span.test.ts
• Original feature-request Stack trace for "Can not execute the operation on ended Span" log #5105

[Victorsesan]

@pichlermarc Still up for grabs? Would give it a try

[pichlermarc]

yep, still up-for-grabs 👍
It's yours - thanks for working on this 🙂

[Victorsesan]

👋 @pichlermarc my first shot on this up for review.

[pichlermarc]

@Victorsesan the commit you linked looks good % the changes to package.json, which should not be needed for this - would you mind opening a pull request? 🙂