chore: bump hyper to 1.0.1

[mraszyk]

This PR bumps hyper to 1.0.1.

[adamspofford-dfinity]

Is this prompted by something? Otherwise I would prefer to keep 0.14 until reqwest updates to hyper 1.0, so there is only one copy in the tree.

[mraszyk]

Is this prompted by something? Otherwise I would prefer to keep 0.14 until reqwest updates to hyper 1.0, so there is only one copy in the tree.

This blocks bumping axum to 0.7 in icx-proxy. [BOUN-1008]

[adamspofford-dfinity]

These should all be optional dependencies too.

[mraszyk]

What do you mean?

[mraszyk]

I've added optional = true to all of them if that's what you mean.

[adamspofford-dfinity]

As in, they should only be enabled when the hyper feature is enabled.

[mraszyk]

Is it ok now?

[adamspofford-dfinity]

This code does not build with --features hyper.

[mraszyk]

This code does not build with --features hyper.

What do you mean? The CI pipeline has succeeded and I could also successfully run cargo build --release --features hyper locally.

[adamspofford-dfinity]

Apologies for not adding detail - the new errors look like this:

error[E0432]: unresolved import `http_body_to_bytes`
 --> ic-agent/src/agent/http_transport/hyper_transport.rs:7:5
  |
7 | use http_body_to_bytes::{http_body_to_bytes, http_body_to_bytes_with_max_length};
  |     ^^^^^^^^^^^^^^^^^^ use of undeclared crate or module `http_body_to_bytes`

Because the optional dependencies were not added to the hyper feature. I am not sure why it is succeeding on your local machine, you may be on a different commit, but it definitely does not succeed on mine. I am fixing the CI to detect this in #528.

[mraszyk]

I could reproduce the build failure and fixed it now.