opentelemetry: prepare for 0.16.0 release

[jtescher]

Breaking changes in this release:

• Upgrade to v0.17.0 of opentelemetry (opentelemetry: Update otel to 0.17.0 #1853)
  For list of breaking changes in OpenTelemetry, see the v0.17.0 changelog.
• Disable the default tracing-log feature (opentelemetry: disable default tracing-log feature #1869)

[jtescher]

@hawkw did we want to move forward with #1869 before merging this one?

[davidbarsky]

@hawkw did we want to move forward with #1869 before merging this one?

I'm not Eliza, but yes.

[davidbarsky]

Once the build passes, I'll merge this.

[hawkw]

I just saw that #1869 just got merged, but I'm not sure if that was actually the correct solution to the problem. Let's take a minute to make sure that change was correct before we publish this release, please.

[jtescher]

Previous Discord comment context

Hi, is it possible to separate log and tracing?
I tried disabling tracing-log but I cannot turn-off default-features of tracing-subscriber which is a dependncy of tracing-opentelemetry

tracing-opentelemetry = { version = "0.16.0", optional = true, default-features = false }
tracing-subscriber = { version = "0.3.6", default-features = false, features = [
    "smallvec",
    "std",
] }

$ cargo tree -i -p tracing-log
tracing-log v0.1.2
└── tracing-subscriber v0.3.6
    ├── mylib
    └── tracing-opentelemetry v0.16.0
        └── mylib

I cannot reproduce that example. E.g. This example Cargo.toml

[package]
name = "test"
version = "0.1.0"
edition = "2021"

[dependencies]
opentelemetry = "0.16.0"
tracing = "0.1.29"
tracing-opentelemetry = { version = "0.16.0", default-features = false }
tracing-subscriber = { version = "0.3.6", default-features = false, features = [ "smallvec", "std", ] }

tracing-log is not included if default-features = false.

$ cargo tree -i -p tracing-log
error: package ID specification `tracing-log` did not match any packages

#1869 was not to fix the above case, but to simply not require opting out explicitly.