Use reqwest-rustls for opentelemetry dependencies

[CaptainJiNX]

This pull request updates the configuration of the OpenTelemetry dependencies in Cargo.toml to improve control over their features and enhance security and compatibility. The main focus is on explicitly disabling default features and enabling specific features for the opentelemetry-otlp and opentelemetry-zipkin crates.

Dependency configuration updates:

• Cargo.toml: Disabled default features for both opentelemetry-otlp and opentelemetry-zipkin, and explicitly enabled the reqwest-blocking-client and reqwest-rustls features to ensure the use of the Rustls TLS backend and blocking HTTP client.

[Copilot]

Pull request overview

This PR tightens OpenTelemetry exporter dependency configuration to force reqwest to use the Rustls TLS backend (and a blocking HTTP client where applicable) by disabling default features and enabling explicit feature sets for opentelemetry-otlp and opentelemetry-zipkin.

Changes:

• Updated opentelemetry-otlp to default-features = false and enabled http-proto, grpc-tonic, reqwest-blocking-client, and reqwest-rustls.
• Updated opentelemetry-zipkin to default-features = false and enabled reqwest-blocking-client and reqwest-rustls (still optional behind the zipkin feature).
• Refreshed Cargo.lock to reflect the TLS backend switch (removing native-tls/OpenSSL-related crates and resolving to hyper-rustls/rustls).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
Cargo.toml	Disables default features and explicitly enables Rustls + blocking reqwest client features for OTLP/Zipkin crates.
Cargo.lock	Updates the resolved dependency graph consistent with moving from native-tls/OpenSSL to rustls/hyper-rustls.

[lbeschastny]

Closing in favour of #196