Upgrade to opentelemetry 0.25

[ymgyt]

Motivation

Update opentelemetry depencencies to 0.25
https://github.com/open-telemetry/opentelemetry-rust/releases/tag/opentelemetry-0.25.0

From version 0.25, OpenTelemetry started using a unified version across all crates.
open-telemetry/opentelemetry-rust#2084

Solution

• Upgrade opentelemetry deps to 0.25
• Remove AttributeSet from tests
  • Update visibility of AttributeSet from pub to pub(crate) open-telemetry/opentelemetry-rust#2045
• Rename deprecated deployment.environment semantic conv to deployment.environment.name
  • https://opentelemetry.io/docs/specs/semconv/attributes-registry/enduser/

[ymgyt]

I don’t understand the issue yet, but the test failed because the order of attributes in the exported metrics differed each time. Therefore, I added a sorting process during the assertion.

[djc]

Thanks for working on this! I think this is mostly looking good, but I'd like to have a cleaner commit history where basically each commit could pass CI (though I won't ask you to actually test this). As such:

• Please have reorder the commits to put the clippy commit first, as I assume this is independent of the opentelemtry upgrade
• Please squash the commit with the dependency bump with the commit that fixes the tests, also include the commit for fixing the warnings from deprecations
• Add a version bump for this crate into the commit that updates the CHANGELOG

[ymgyt]

Thank you for your review.
I first made a commit addressing Clippy warnings.
I squashed the commits for the OpenTelemetry version bump and deprecation fixes.
I also updated the changelog and bumped the crate version.

[djc]

• Published tracing-opentelemetry v0.26.0 at registry crates-io
• [new tag] v0.26.0 -> v0.26.0
• Release notes

[ymgyt]

@djc
Sorry for the issue with the CHANGELOG update not being as intended. In the PR, I mistakenly created it as:

[Unreleased]

but it should have been:

0.26.0 (September 10, 2024).

Should I create a PR to address this now?

https://github.com/tokio-rs/tracing-opentelemetry/blob/v0.26.0/CHANGELOG.md

[djc]

Yes, please.