docs: Add reqwest-tracing to related crates in README

[tl-rodrigo-gryzinski]

Add reqwest-tracing to the list of related crates.

[hawkw]

Thanks for adding your crate!

There's also a copy of the same list in the lib.rs docs for the tracing crate, here:

tracing/tracing/src/lib.rs

Lines 770 to 812 in 1215ab2

	//! Additionally, there are also several third-party crates which are not
	//! maintained by the `tokio` project. These include:
	//!
	//! - [`tracing-timing`] implements inter-event timing metrics on top of `tracing`.
	//! It provides a subscriber that records the time elapsed between pairs of
	//! `tracing` events and generates histograms.
	//! - [`tracing-opentelemetry`] provides a subscriber for emitting traces to
	//! [OpenTelemetry]-compatible distributed tracing systems.
	//! - [`tracing-honeycomb`] Provides a layer that reports traces spanning multiple machines to [honeycomb.io]. Backed by [`tracing-distributed`].
	//! - [`tracing-distributed`] Provides a generic implementation of a layer that reports traces spanning multiple machines to some backend.
	//! - [`tracing-actix-web`] provides `tracing` integration for the `actix-web` web framework.
	//! - [`tracing-actix`] provides `tracing` integration for the `actix` actor
	//! framework.
	//! - [`tracing-gelf`] implements a subscriber for exporting traces in Greylog
	//! GELF format.
	//! - [`tracing-coz`] provides integration with the [coz] causal profiler
	//! (Linux-only).
	//! - [`tracing-bunyan-formatter`] provides a layer implementation that reports events and spans
	//! in [bunyan] format, enriched with timing information.
	//! - [`tracing-wasm`] provides a `Collect`/`Subscribe` implementation that reports
	//! events and spans via browser `console.log` and [User Timing API (`window.performance`)].
	//! - [`tracing-web`] provides a layer implementation of level-aware logging of events
	//! to web browsers' `console.*` and span events to the [User Timing API (`window.performance`)].
	//! - [`tide-tracing`] provides a [tide] middleware to trace all incoming requests and responses.
	//! - [`test-log`] takes care of initializing `tracing` for tests, based on
	//! environment variables with an `env_logger` compatible syntax.
	//! - [`tracing-unwrap`] provides convenience methods to report failed unwraps
	//! on `Result` or `Option` types to a [`collect`].
	//! - [`diesel-tracing`] provides integration with [`diesel`] database connections.
	//! - [`tracing-tracy`] provides a way to collect [Tracy] profiles in instrumented
	//! applications.
	//! - [`tracing-elastic-apm`] provides a layer for reporting traces to [Elastic APM].
	//! - [`tracing-etw`] provides a layer for emitting Windows [ETW] events.
	//! - [`tracing-fluent-assertions`] provides a fluent assertions-style testing
	//! framework for validating the behavior of `tracing` spans.
	//! - [`sentry-tracing`] provides a layer for reporting events and traces to [Sentry].
	//! - [`tracing-forest`] provides a subscriber that preserves contextual coherence by
	//! grouping together logs from the same spans during writing.
	//! - [`tracing-loki`] provides a layer for shipping logs to [Grafana Loki].
	//! - [`tracing-logfmt`] provides a layer that formats events and spans into the logfmt format.
	//!
	//! If you're the maintainer of a `tracing` ecosystem crate not listed above,
	//! please let us know! We'd love to add your project to the list!

would you mind adding a link there as well? Thanks!

(we really should get around to using #[doc = include_str!(...)] to avoid having to duplicate stuff between the README and lib docs...)

[tl-rodrigo-gryzinski]

Thanks @hawkw, added the crate to the module docs and committed your suggestions

[hawkw]

thanks, this looks good to me!