tech debt: connection handler implementation

[lambdai]

ConnectionHandlerImpl maintains the active listeners per worker thread.

Envoy has two categories of listener, tcp series and udp series. From the view of worker, both categories share the same interface: start, stop ...

It's a different story from the perspective of a listener.
Currently,

1. udp listener put udp related function into ConnectionHandler interface.

2. ActiveTcpListener is an internal class of ConnectionHandlerImpl and it depends on the implementation of ConnectionHandler instead of the interface. This is a huge pain. To test an ActiveTcpListener we have to push a long way from a listener config. It's hard to manipulate the internal state of a ActiveTcpListener obj, or a udp listener.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[lambdai]

wip