Upgrade the `http` crate to version 1.0.0

[bruceg]

This requires updating several crates simultaneously, only some of which currently have updates to their http dependencies. I will update this issue as the dependency crates are bumped:

• azure-sdk-for-rust Maybe done in Redefine Method, StatusCode from http_types in typespec Azure/azure-sdk-for-rust#2331
• axum v0.7.0
• h2 v0.4.0
• headers v0.4.0
• http v1.0.0
• http-body v1.0.0
• http-serde v2.0.0
• http-types
  • Fix is The http dependency needs updating to v1.0.0 http-rs/http-types#520 but repo is abandoned
  • No longer used by newest azure crate so N/A once azure crates are updated
• hyper v1.0.1
• hyper-openssl v0.10.1
• hyper-proxy
  • tafia/hyper-proxy/issues/42 but repo is abandoned
  • Replace with hyper-proxy2 or hyper-http-proxy which are maintained compatible forks
• tonic v0.12.0
• tower-http v0.5.0

[pront]

Seems like https://crates.io/crates/http-types and https://crates.io/crates/hyper-proxy are on the latest version.

Also, https://crates.io/crates/tokio-tungstenite (PR) is another crate that seems to affected by the http upgrade.

[bruceg]

Yes, both http-types and hyper-proxy do not have a released version that upgrades their usage to http 1.0. So, we are using their latest versions, but upgrading the other crates without those breaks the build.

Agreed, at least part of the tokio-tungstenite breakage is caused by this issue. I'll add that to the list.

[bruceg]

Note that hyper-proxy appears to be unmaintained, as the last commit was 3 years ago, which may require converting Vector to use hyper-proxy2 (link) or handling proxying manually.

[bruceg]

Similarly, the last commit to http-types was 2 years ago, but replacing it will be more difficult as it is depended on by azure_core and wiremock.