Rename HyperHttpTransport

[sjwiesman]

HyperHttpTransport is really a bridge between the flink runtime and the user sdk. It seems strange it exposes the dependency through its name.

[aljoscha]

This was modelled on the existing Python SDK which doesn't prescribe any particular framework for implementing the actual transport. You can see in the example that it uses Flask: https://github.com/apache/flink-statefun/blob/master/statefun-examples/statefun-python-greeter-example/greeter/greeter.py. But I don't think that's the only possible implementation.

I do think that the code is a bit verbose in the Python example, the Rust example is more concise. While I'm not married to the idea of allowing different transports, I see that it could be helpful if people already are in a certain ecosystem and don't want to use Hyper/Tokio.

Side note: I did plan to rename some types because of this lint: https://rust-lang.github.io/rust-clippy/master/index.html#module_name_repetitions

[sjwiesman]

Fair