Change masscan step to accept ranges

[LambdaF]

Range expansion was originally added as the masscan step was meant to be ran asynchronously with a 1 ip to 1 scan mechanism (as with the nmap step).
Synchronous masscan doesn't work well, so it would be ideal to refactor the masscan step to accept ranges once again without expansion.
Furthermore, this reduces headaches of strings taking up a lot of memory for certain range sizes, at least in the first instance (e.g. /8 ranges).