scheduler to reuse existing initial worker-to-scheduler connection

Current dask behavior:
- after start worker connects to scheduler to register. this connection persists.
- scheduler connects to worker back using new connection during the scheduling

To make dask setup "firewall friendly" the proposal is for scheduler to reuse(multiplex) existing initial worker-to-scheduler connection.