Bump priority for scan task in certain situations.

[dougkoellmer]

It's theoretically possible that a scan task is indefinitely subject to line-cutting in the task queue. Perhaps have some time limit (configurable) past which (if we're autoscanning or infinitely scanning) the scan task is given the same priority as reads/writes. Also argument to be made that an explicit startScan() call should have a higher priority as well.