tracing: update tracing-opentelemetry with panic fix

[guswynn]

Alright, this is a doozy:

The bottom commit is primarily bringing in tokio-rs/tracing-opentelemetry#86, through:

• this cherry-pick on our fork: MaterializeInc/tracing-opentelemetry@1e0cf8b
• a merge to get back to upstream: MaterializeInc/tracing-opentelemetry@1c87231 @ParkMyCar this has some changes in src/layer.rs that I needed to refactor, particularly your tests and the on_event code!

the bottom commit also updates various related crates to the new version that tracing-opentelemetry uses.

The second commit attempts to resolve conflicts for ordered-float;

The 3rd commit certifies the new deps with cargo-vet (it adds an exemption for the new serde-value version from our fork that just bumps its ordered-float dep)

Motivation

• This PR fixes a recognized bug.

Fixes https://github.com/MaterializeInc/database-issues/issues/4358

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• This PR includes the following user-facing behavior changes:

[ParkMyCar]

1. Upgrade in MaterializeInc/tracing-opentelemetry@1c87231 looks good
2. One thought on the on_follows_from API, no idea if the scenario I'm thinking of is possible though!

Otherwise things look good, excited that we finally tracked down this issue!! 💯

[guswynn]

updated with MaterializeInc/tracing-opentelemetry#1

[guswynn]

@ParkMyCar Im gonna merge this so we try it out, but let me think more about: MaterializeInc/tracing-opentelemetry@1e0cf8b#r136643682