Bump opentelemetry to 0.23 (#1160)

And bump other opentelemetry-* deps to compatible with 0.23

<!-- The PR description should answer 2 important questions: -->

### What

<!-- What is this PR trying to accomplish (and why, if it's not
obvious)? -->

<!-- Consider: do we need to add a changelog entry? -->

<!-- Does this PR introduce new validation that might break old builds?
-->

<!-- Consider: do we need to put new checks behind a flag? -->
Need
[add_link](https://docs.rs/opentelemetry/0.23.0/opentelemetry/trace/trait.Span.html#tymethod.add_link)
API on Spans for tracing `graphql-ws` websockets code. It is available
opentelementry version `0.23` and above. This also bumps all the
dependents of the opentelemetry crate (`opentelemetry-*`)

### How

<!-- How is it trying to accomplish it (what are the implementation
steps)? -->
By updating root `Cargo.toml`.

V3_GIT_ORIGIN_REV_ID: 87c1bedde35f5e8e91366aceb1379ab5d43b5b99

v3/Cargo.toml

@@ -109,14 +109,14 @@ mimalloc = "0.1"
 mockito = { version = "~1.4", default-features = false } # v1.5+ depends on http v1
 nonempty = "0.10"
 openssl = "0.10"
-opentelemetry = "0.22"
-opentelemetry-contrib = "0.14"
-opentelemetry-http = "0.11"
-opentelemetry-otlp = "0.15"
-opentelemetry-semantic-conventions = "0.14"
-opentelemetry-stdout = { version = "0.3", default-features = false }
-opentelemetry-zipkin = "0.20"
-opentelemetry_sdk = "0.22"
+opentelemetry = "0.23"
+opentelemetry-contrib = "0.15"
+opentelemetry-http = "0.12"
+opentelemetry-otlp = "0.16"
+opentelemetry-semantic-conventions = "0.15"
+opentelemetry-stdout = { version = "0.4", default-features = false }
+opentelemetry-zipkin = "0.21"
+opentelemetry_sdk = "0.23"
 postcard = "1"
 pretty_assertions = "1"
 proc-macro2 = "1"