chore(deps): bump opentelemetry_sdk from 0.21.2 to 0.22.1

[dependabot[bot]]

Bumps opentelemetry_sdk from 0.21.2 to 0.22.1.

Release notes

Sourced from opentelemetry_sdk's releases.

0.22.1 of OpenTelemetry sdk

Fixed open-telemetry/opentelemetry-rust#1576 Fix Span kind is always set to "internal".

v0.22.0

API

Added

• open-telemetry/opentelemetry-rust#1410 Add experimental synchronous gauge. This is behind the feature flag, and can be enabled by enabling the feature otel_unstable for opentelemetry crate.

• open-telemetry/opentelemetry-rust#1410 Guidelines to add new unstable/experimental features.

Changed

• Modified AnyValue.Map to be backed by HashMap instead of custom OrderMap, which internally used IndexMap. There was no requirement to maintain the order of entries, so moving from IndexMap to HashMap offers slight performance gains, and avoids IndexMap dependency. This affects body and attributes of LogRecord. open-telemetry/opentelemetry-rust#1353
• Add TextMapCompositePropagator open-telemetry/opentelemetry-rust#1373
• Turned off events for NoopLogger to save on operations open-telemetry/opentelemetry-rust#1455

Removed

• Removed OrderMap type as there was no requirement to use this over regular HashMap. open-telemetry/opentelemetry-rust#1353
• Remove API for Creating Histograms with signed integers. open-telemetry/opentelemetry-rust#1371
• Remove global::shutdown_meter_provider, use SdkMeterProvider::shutdown directly instead (#1412).

SDK

Deprecated

• XrayIdGenerator in the opentelemetry-sdk has been deprecated and moved to version 0.10.0 of the opentelemetry-aws crate.

Added

• #1410 Add experimental synchronous gauge

• #1471 Configure batch log record processor via OTEL_BLRP_* environment variables and via OtlpLogPipeline::with_batch_config

• #1503 Make the documentation for In-Memory exporters visible.

• #1526 Performance Improvement : Creating Spans and LogRecords are now faster, by avoiding expensive cloning of Resource for every Span/LogRecord.

Changed

• Breaking #1313 #1350 Changes how Span links/events are stored to achieve performance gains. See below for details:

  Behavior Change: When enforcing max_links_per_span, max_events_per_span from SpanLimits, links/events are kept in the first-come order. The previous "eviction" based approach is no longer performed.

  Breaking Change Affecting Exporter authors:

  SpanData now stores links as SpanLinks instead of EvictedQueue where SpanLinks is a struct with a Vec of links and dropped_count.

... (truncated)

Commits

• 19b9878 Prepare for SDK 0.22.1 hotfix release (#1579)
• 5542f37 Fix span kind being always internal (#1576)
• ab9415a Bump versions to prepare for release v0.22 (#1539)
• 6422524 fix: disable workspace default feature (#1562)
• d88e83d Fix invalid import paths under "Getting Started" (#1574)
• 27cf653 Deprecate AWS XrayIdGenerator (#1573)
• 188a26c Switch from the chrono clock feature to now (#1569)
• 47b928e Disable default features on reqwest (#1570)
• 98cd103 chore: skip coverage check for dependencies update (#1558)
• 36c2a8e deprecation(opentelemetry-jaeger): Add deprecation notice. (#1560)
• Additional commits viewable in compare view

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)

[mergify[bot]]

@dependabot[bot] Convert your pr to draft since CI failed

[mergify[bot]]

@dependabot[bot] Your PR is in conflict and cannot be merged.

[mergify[bot]]

@dependabot[bot] Convert your pr to draft since CI failed

[mergify[bot]]

@dependabot[bot] Convert your pr to draft since CI failed

[mergify[bot]]

@dependabot[bot] You've modified the workflows. Please don't forget to update the .mergify.yml.

[mergify[bot]]

@dependabot[bot] Convert your pr to draft since CI failed

[Phoenix500526]

Duplicated with #794

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.