Update opentelemetry-dotnet monorepo to 1.17.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
OpenTelemetry.Api (source)	1.15.3 → 1.17.0
OpenTelemetry.Exporter.InMemory (source)	1.15.3 → 1.17.0

---

Release Notes

open-telemetry/opentelemetry-dotnet (OpenTelemetry.Api)

v1.17.0

Release details: 1.17.0

• Added support for a Schema URL on Resource instances.
• The Resource Schema URL is now printed alongside the resource attributes
  when using the Console and OTLP exporters.
• Added ExcludedTagKeys property to MetricStreamConfiguration to support
  excluding specific tag keys from metric streams.
• Updated tracestate key validation to comply with the W3C Trace Context
  Level 2 grammar.
• The SDK now depends on Microsoft.Extensions.Configuration.EnvironmentVariables
  instead of using a vendored implementation.
• All libraries are now marked as trim and AOT compatible.
• Fixed a metric storage leak that occurred when meters and instruments were
  repeatedly created and disposed.
• Fixed TraceContextPropagator to normalize empty tracestate header values
  to null when extracting trace context.
• Fixed OtlpLogExporter so OtlpExporterOptions.ExportProcessorType and
  OtlpExporterOptions.BatchExportProcessorOptions are respected when
  LogRecordExportProcessorOptions are not configured.
• Fixed the OTLP exporter dropping retryable data instead of saving it to disk
  when persistent storage retry is enabled and an export exceeds the configured
  timeout.
• Fixed the OTLP/HTTP exporter silently dropping data when an export timed out.
• Fixed the OTLP/gRPC exporter logging incorrectly when an export timed out.
• Performance and memory improvements for the OTLP exporter when exporting logs
  and metrics.

v1.16.0

Release details: 1.16.0

• Breaking Change Explicit histogram boundaries no longer allow more than
  10 million values.
• Fix BaggagePropagator to correctly follow Key and Value Encoding rules.
• Add support for the W3C randomness flag.
• Fixed TraceContextPropagator to deduplicate duplicate tracestate keys.
• ObservedTimestamp will now be exported for logs in the console exporter.
• Fixed NullReferenceException when exporting OTLP logs if the scope key is
  null.
• Added opt-in support for gzip compression to the OTLP exporter.
• Fixed OTLP disk retry data being stored incorrectly when using persistent
  storage retry.
• Fixed OtlpLogExporter integration with IHttpClientFactory.
• Do not enable the OTLP integration with IHttpClientFactory when mTLS is
  enabled.
• Handle Retry-After response headers that specify a date instead of a delay.
• observed_time_unix_nano will no longer always be identical to time_unix_nano
  when using the logs bridge API.
• Stop validating View-provided metric stream Name against the instrument name
  syntax.
• Fix incorrect validation of OTEL_BSP_* and OTEL_BLRP_* environment variables.
• Fix observable instrument callbacks running once per reader instead of once per
  collection cycle.
• Added exception safety for user-supplied ExemplarReservoir implementations.
• Fixed a circular reference which could cause a LoggerProvider to fail to
  resolve when one of its dependencies depends on ILogger or ILoggerFactory.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

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

[coderabbitai]

Warning

Review limit reached

@renovate[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 43d7a4c1-4dba-44c4-8498-421492375c9e

📥 Commits

Reviewing files that changed from the base of the PR and between 531cd59 and 0da0dcc.

📒 Files selected for processing (2)

• src/Cassandra.IntegrationTests/Cassandra.IntegrationTests.csproj
• src/Extensions/Cassandra.OpenTelemetry/Cassandra.OpenTelemetry.csproj

---

_{Comment @coderabbitai help to get the list of available commands.}