Bump hyper version to v1

[shunsukew]

Resolve #185

The latest jsonrpsee release bumped its dependency hyper's version to v1.
https://github.com/paritytech/jsonrpsee/releases/tag/v0.23.0

This introduced low level api removal such as hyper::service::make_service_fn, and some others. See https://hyper.rs/guides/1/upgrading/. SubwayServerBuilder build function need to be updated accordingly.

Because we want to make use of a new feature added to jsonrpsee, hyper version upgrades is required as a first step.
paritytech/jsonrpsee#1388
paritytech/jsonrpsee#1389

[shunsukew]

For some reason, test doesn't finish on my local env. but don't know at which one it is stacking.
I’m checking now

[shunsukew]

Specifying port 0 in tests merge_subscription_works and upstream_error_propagate seem causing this issue.
During tests connecting to addr 0.0.0.0:0 will have below error and forever looping try to establish a ws connection to upstream server at WsClientBuilder.

2024-06-08T12:21:43.712626Z  INFO subway::extensions::client: Connecting to endpoint: ws://0.0.0.0:0
2024-06-08T12:21:43.712626Z  INFO subway::extensions::client: Connecting to endpoint: ws://0.0.0.0:0
2024-06-08T12:21:43.713347Z  WARN subway::extensions::client: Unable to connect to endpoint: 'ws://0.0.0.0:0' error: Error when opening the TCP socket: Can't assign requested address (os error 49)

@xlc Why port 0 is used for those tests?

[xlc]

port 0 usually means let the system to allocate an unused port

[shunsukew]

port 0 usually means let the system to allocate an unused port

I see, in that case, the cause is really clear. I needed to return addr with actual allocated port.
Thank you so much