chore(deps): bump @opentelemetry/sdk-node from 0.38.0 to 0.51.0 in /src/checkout

[dependabot]

Bumps @opentelemetry/sdk-node from 0.38.0 to 0.51.0.

Release notes

Sourced from @​opentelemetry/sdk-node's releases.

Experimental v0.51.0

0.51.0

💥 Breaking Change

• feat(sdk-node)!: remove long deprecated methods in favor of constructor options #4606 @​pichlermarc
  • NodeSDK.configureTracerProvider(), please use constructor options instead
  • NodeSDK.configureMeterProvider(), please use constructor options instead
  • NodeSDK.configureLoggerProvider(), please use constructor options instead
  • NodeSDK.addResource(), please use constructor options instead
  • NodeSDK.detectResources(), this is not necessary anymore, resources are now auto-detected on NodeSDK.start() if the constructor option autoDetectResources is unset, undefined or true.
• feat(instrumentation): add patch and unpatch diag log messages #4641
  • Instrumentations should not log patch and unpatch messages to diag channel.
• feat!(instrumentation): remove moduleExports generic type from instrumentation registration #4598 @​blumamir
  • breaking for instrumentation authors that depend on
    • InstrumentationBase
    • InstrumentationNodeModuleDefinition
    • InstrumentationNodeModuleFile

🚀 (Enhancement)

• refactor(instrumentation-grpc): move to use SEMATTRS #4633
• feat(otlp-transformer): consolidate scope/resource creation in transformer #4600
• feat(sdk-logs): print message when attributes are dropped due to attribute count limit #4614 @​HyunnoH
• feat(sdk-node): add usage for the detector ServiceInstanceIdDetectorSync. #4626 @​maryliag
  • The resource detector can be added to default resource detector list by adding the value serviceinstance to the list of resource detectors on the environment variable OTEL_NODE_RESOURCE_DETECTORS, e.g OTEL_NODE_RESOURCE_DETECTORS=env,host,os,serviceinstance
  • The value can be overwritten by
    • merging a resource containing the service.instance.id attribute
    • using another resource detector which writes service.instance.id

🐛 (Bug Fix)

• fix(otlp-grpc-exporter-base): avoid TypeError on exporter shutdown #4612 @​pichlermarc
• fix(instrumentation): Don't use require to load package.json files #4593 @​timfish

Experimental v0.50.0

0.50.0

💥 Breaking Change

• fix(exporter-*-otlp-grpc)!: lazy load gRPC to improve compatibility with @opentelemetry/instrumenation-grpc #4432 @​pichlermarc
  • Fixes a bug where requiring the gRPC exporter before enabling the instrumentation from @opentelemetry/instrumentation-grpc would lead to missing telemetry
  • Breaking changes, removes several functions and properties that were used internally and were not intended for end-users
    • getServiceClientType()
      • this returned a static enum value that would denote the export type (SPAN, METRICS, LOGS)
    • getServiceProtoPath()
      • this returned a static enum value that would correspond to the gRPC service path
    • metadata
      • was used internally to access metadata, but as a side effect allowed end-users to modify metadata on runtime.
    • serviceClient

... (truncated)

Commits

• 3ab4f76 chore: prepare release 1.24.0/0.51.0 (#4650)
• 31eb60d feat!(instrumentation): add patch and unpatch diag log messages (#4641)
• 99431df feat!(instrumentation): remove moduleExports generic type from instrumentatio...
• 73fddf9 feat(sdk-node): add serviceInstanceIdDetector to NodeSDK (#4626)
• 0d6c456 fix(deps): update dependency axios to v1.6.0 [security] (#4639)
• 2610122 fix: revert modifications to Apache license (#4640)
• 629bb83 chore(deps): lock file maintenance (#4634)
• 0a750eb refactor(instr-grpc): move to use SEMATTRS (#4633)
• 7f82b80 Move xray propagator from contrib (no history) (#4603)
• 87e25c5 fix: ensure api is not dropped from workspaces in package-lock.json (#4623)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by pichlermarc, a new releaser for @​opentelemetry/sdk-node since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #546.