Factoring out hyper into rapira_net crate

[rauanmayemir]

Currently, http plugin carries all the plumbing for the HTTP plugin. When gRPC enters the fold, it could re-use that same plumbing.

What if there was a rapira_net crate that collected all the inbound networking related code AND also middleware/interceptor 'interfaces'?

I remember roadrunner having all common interfaces in sort of 'api' module which was also used for everything. I'd want to avoid this in rapira and let all the http/grpc/ws inbound stuff have its own pace in 'net' module.

At least initially, when the design is not cemented.

[rustatian]

Hey @rauanmayemir 👋🏻
Sorry, missed that message. For the rapira_net - yes, I already have this crate for epoll and other common net stuff.
APIs (including middleware/interceptor traits) are in the api crate. But they're not stabilized yet.