fix(deps): update opentelemetry-rust monorepo

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry	dependencies	minor	0.23.0 -> 0.24.0
opentelemetry-appender-tracing (source)	dependencies	minor	0.4.0 -> 0.5.0
opentelemetry-http	dependencies	minor	0.12.0 -> 0.13.0
opentelemetry-otlp (source)	dependencies	minor	0.16.0 -> 0.17.0
opentelemetry-prometheus	dependencies	minor	0.16.0 -> 0.17.0
opentelemetry-semantic-conventions (source)	dependencies	minor	0.15.0 -> 0.16.0
opentelemetry-stdout (source)	dependencies	minor	0.4.0 -> 0.5.0
opentelemetry_sdk	dependencies	minor	0.23.0 -> 0.24.0

---

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.24.0

Compare Source

See individual crate changelogs for details.

open-telemetry/opentelemetry-rust (opentelemetry-appender-tracing)

v0.5.0

Compare Source

• 1869 Utilize the LogRecord::set_target() method to pass the tracing target to the SDK.
  Exporters might use the target to override the instrumentation scope, which previously contained "opentelemetry-appender-tracing".

• Breaking 1928 Insert tracing event name into LogRecord::event_name instead of attributes.

  • If using a custom exporter, then they must serialize this field directly from LogRecord::event_name instead of iterating over the attributes. OTLP Exporter is modified to handle this.

• Update opentelemetry dependency version to 0.24

open-telemetry/opentelemetry-rust (opentelemetry-otlp)

v0.17.0

Compare Source

• Add "metrics", "logs" to default features. With this, default feature list is
  "trace", "metrics" and "logs".
• OtlpMetricPipeline.build() no longer invoke the
  global::set_meter_provider. User who setup the pipeline must do it
  themselves using global::set_meter_provider(meter_provider.clone());.
• Add with_resource on OtlpLogPipeline, replacing the with_config method.
  Instead of using
  .with_config(Config::default().with_resource(RESOURCE::default())) users must
  now use .with_resource(RESOURCE::default()) to configure Resource when using
  OtlpLogPipeline.
• Breaking The methods OtlpTracePipeline::install_simple() and OtlpTracePipeline::install_batch() would now return TracerProvider instead of Tracer.
  These methods would also no longer set the global tracer provider. It would now be the responsibility of users to set it by calling global::set_tracer_provider(tracer_provider.clone());. Refer to the basic-otlp and basic-otlp-http examples on how to initialize OTLP Trace Exporter.
• Breaking Correct the misspelling of "webkpi" to "webpki" in features #​1842
• Bump MSRV to 1.70 #​1840
• Fixing the OTLP HTTP/JSON exporter. #​1882 - The exporter was broken in the
  previous release.
• Breaking 1869 The OTLP logs exporter now overrides the InstrumentationScope::name field with the target from LogRecord, if target is populated.
• Groups batch of LogRecord and Span by their resource and instrumentation scope before exporting, for better efficiency #​1873.
• Breaking Update to http v1 and tonic v0.12 #​1674
• Update opentelemetry dependency version to 0.24
• Update opentelemetry_sdk dependency version to 0.24
• Update opentelemetry-http dependency version to 0.13
• Update opentelemetry-proto dependency version to 0.7

open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)

v0.16.0

Compare Source

Changed

• Breaking Moved duplicated (and unrelated) attributes from opentelemetry_semantic_conventions::trace and opentelemetry_semantic_conventions::resource into opentelemetry_semantic_conventions::attribute (which now contains all semantic attributes). trace and resource now only contain references to attributes which fall under their respective category.

Added

• Created opentelemetry_semantic_conventions::metric to store metric semantic conventions.

open-telemetry/opentelemetry-rust (opentelemetry-stdout)

v0.5.0

Compare Source

• Update opentelemetry dependency version to 0.24
• Update opentelemetry_sdk dependency version to 0.24

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path tailcall-upstream-grpc/Cargo.toml --package [email protected] --precise 0.24.0
    Updating crates.io index
error: failed to select a version for the requirement `opentelemetry = "^0.23.0"`
candidate versions found which didn't match: 0.24.0
location searched: crates.io index
required by package `async-graphql v7.0.7`
    ... which satisfies dependency `async-graphql = "^7.0.3"` (locked to 7.0.7) of package `tailcall v0.1.0 (/tmp/renovate/repos/github/tailcallhq/tailcall)`

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.24.0
    Updating crates.io index
error: failed to select a version for the requirement `opentelemetry = "^0.23.0"`
candidate versions found which didn't match: 0.24.0
location searched: crates.io index
required by package `async-graphql v7.0.7`
    ... which satisfies dependency `async-graphql = "^7.0.3"` (locked to 7.0.7) of package `tailcall v0.1.0 (/tmp/renovate/repos/github/tailcallhq/tailcall)`