chore: refresh subcrate Cargo.locks to crates.io opentelemetry 0.32.1

[mheffner]

Summary

Commit 39c08e2 migrated the opentelemetry dependencies from a git rev to crates.io, but only regenerated the root Cargo.lock. The subcrate and example lockfiles were left stale. This refreshes them so opentelemetry_sdk resolves to 0.32.1 from crates.io consistently everywhere.

Staleness found

Lock file	Before	After
utilities/Cargo.lock	0.31.0 (git rev 0948c61)	0.32.1 (crates.io)
rotel_rust_processor_sdk/Cargo.lock	0.31.0 (git rev)	0.32.1 (crates.io)
rotel_python_processor_sdk/Cargo.lock	0.32.1 (git rev 284a37d9)	0.32.1 (crates.io)
examples/rust_processors/async_enrichment_processor/Cargo.lock	0.31.0 (git rev)	0.32.1 (crates.io)
examples/rust_processors/trivial_processor/Cargo.lock	0.31.0 (git rev)	0.32.1 (crates.io)

The root Cargo.lock was already current and is unchanged.

Two kinds of staleness:

• utilities, rust_sdk, both examples — locked to opentelemetry 0.31.0 from a git rev, while their Cargo.toml already required opentelemetry-proto = "0.32.0" (an outright mismatch).
• python_sdk — already 0.32.1 but still sourced from a git rev instead of crates.io.

How

Ran cargo update in each affected crate directory. thiserror/thiserror-impl also bumped to 2.0.19 as a side effect. Verified with cargo tree --locked -i opentelemetry_sdk in each crate — all resolve to 0.32.1 and lock check passes.