Support using the `aws-lc-rs` cryptographic crate

[GeorgeHahn]

Is your feature request related to a problem? Please describe.
This crate currently hardcodes ring as its only supported crypto implementation. The ring crate is in maintenance mode and much of the ecosystem has moved over to the better supported aws-lc-rs crate.

This is a challenge for my team, as we maintain a number of Rust services in production. We ban ring from our dependency tree to ensure we're using a single crypto provider across the board. That gives us less risk, less complexity, and faster builds.

Describe the solution you'd like
Support using aws-lc-rs as a rustls crypto provider.

There are a number of ways to enable this. Two notable options are a 'no provider' feature that allows users to set the global rustls crypto provider, or by providing a specific aws-lc-rs feature.

Additional context
This may be incoming by default in a future reqwest version. More info in Sean McArthur's blog post here.

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.