Pipelined request hangs after the idle connection closes #552

PipelineClient stops its worker when the connection has been idle, but leaves the request channels set. The next request is written to those channels and blocks, because a new worker is started only when the channels are nil. If a request is still queued, the channels are discarded and that request never returns. Nuclei templates with pipeline enabled hang when two sends are further apart than the idle timeout.