Bump version of hyper from 0.14 to 1.0

[fuyufjh]

Hyper 1.0 has released. It seems that 0.14.x branch won't be updated any longer, so let's migrate to 1.0.

https://github.com/hyperium/hyper/releases

Be sure to checkout the upgrading guide!

Related dependencies that might need to be upgraded together:

• axum
• http
• tonic

---

@BugenZhao External blockers:

• Support hyper 1.0 hyperium/tonic#1307
• [tracking] support hyper/http/etc. 1.0 awslabs/aws-sdk-rust#977
• Tracking issues of upgrade hyper and its ecosystem to 1.0 apache/opendal#3643
• chore(dep): bump arrow-udf-flight #17544
• chore!: bump tonic to 0.12 for hyper 1.0 ecosystem TrueLayer/ginepro#57 (comment)
• bump tonic to 0.12 and prost to 0.13 for arrow-flight apache/arrow-rs#6041
• chore: bump tonic to v0.12 & etcd-client to v0.14 madsim-rs/madsim#222

[fuyufjh]

Block on hyperium/tonic#1307

A PR WIP: hyperium/tonic#1595

[BugenZhao]

Waiting for a new release of tonic: hyperium/tonic#1734

[BugenZhao]

Waiting for a new release of tonic: hyperium/tonic#1734

Released 0.12. Let's do it!

Progress:

• chore!: bump tonic to 0.12 for hyper 1.0 ecosystem TrueLayer/ginepro#57 (comment)
• refactor(meta): use upstream version of etcd-client #17648
• bump tonic to 0.12 and prost to 0.13 for arrow-flight apache/arrow-rs#6041
• ...

[BugenZhao]

The major blocker now is the resolution conflict with the dependencies specified as =x.y.z in arrow-udf-deno -> deno-xxx. After some consideration, I think we have to

• either bump the deno version in arrow-udf-deno, which requires some advanced knowledge of deno internals
• or drop its support as in chore(dep): bump arrow-udf-flight #17544

[fuyufjh]

The major blocker now is the resolution conflict with the dependencies specified as =x.y.z in arrow-udf-deno -> deno-xxx. After some consideration, I think we have to

• either bump the deno version in arrow-udf-deno, which requires some advanced knowledge of deno internals
• or drop its support as in chore(dep): bump arrow-udf-flight #17544

+1 for dropping the dependency. Introducing deno as a dependency is more painful than we thought before.