Switch Honeycomb integration to use Opentelemetry

[Fishrock123]

Honeycomb is slowly switching to opentelemetry and so should this.

The current honeycomb impl this runs on top of (libhoney-rust) has some issues (inefficiencies, and is likely memory leak source).

Here are some links:

• https://crates.io/crates/opentelemetry
• https://crates.io/crates/tracing-opentelemetry

Basically, it needs a tracing subscriber which feeds into opentelemetry.

Additionally there are these but they might already be covered in the tracing integration.

• https://crates.io/crates/opentelemetry-tide
  https://crates.io/crates/opentelemetry-surf

[Fishrock123]

For more information about how the tracing parts work, see it's readme: https://crates.io/crates/tracing

[Fishrock123]

Here is how it is currently wired up:

trace::info! -> tracing (crate) -> tracing-honeycomb (crate, implements tracing-subscriber) -> tracing-distributed (crate) -> libhoney-rust (crate) -> (http send)

Here is what I think it will look like:

trace::info! -> tracing (crate) -> tracing-opentelemetry (crate, implements tracing-subscriber) -> opentelemetry (crate) -> opentelemtry-oltp (crate) -> (http or grpc send)