Update opentelemetry-semconv to 1.26.0-alpha

[typelevel-steward]

About this PR

📦 Updates io.opentelemetry.semconv:opentelemetry-semconv from 1.25.0-alpha to 1.26.0-alpha

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "io.opentelemetry.semconv", artifactId = "opentelemetry-semconv" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.opentelemetry.semconv", artifactId = "opentelemetry-semconv" }
}]

^{labels: library-update, early-semver-minor, semver-spec-minor, commit-count:n:2}

[iRevive]

The generator produces identical attribute names for both attribute.name and attribute_name. Consequently, if the attribute is renamed (changing _ to . or vice versa), its value changes while its name remains unchanged.

See:

• Semconv codegen should produce different constant names if attribute is renamed _ -> ``  open-telemetry/semantic-conventions-java#75
• messaging.client_id -> messaging.client.id rename causes issues with code generation open-telemetry/semantic-conventions#1031

[iRevive]

The module is experimental and we cannot offer binary guarantees there. It should be safe to disable MiMa checks.

[NthPortal]

sorry I'm so late with pointing this out (was sick), but the since version is wrong

[iRevive]

The value is hardcoded in the template and we cannot determine it dynamically :(
https://github.com/typelevel/otel4s/blob/main/buildscripts/semantic-convention/templates/SemanticAttributes.scala.j2#L88

I guess the best option is to use an empty string instead. At least we will not mislead users.