Tasks that take both pos/name sorted probably need different resources #170
Description
Major culprit here is HTSEQ: https://github.com/stjudecloud/workflows/blob/main/tools/htseq.wdl
It has a pretty terrible sort algorithm and eats up resources when the input is position sorted. We've exposed the name sort option but still allocate a large amount of memory and disk. Neither are likely needed.