Check that outbound nodes are treated the same as whitelisted connections for the purposes of
getdatadelaysAdd test case that demonstrates download retries are preferentially given to outbound (preferred) connections even when multiple announcements are considered ready.
NUM_INBOUND is a magic number large enough that it should fail over 90% of the time
if the underlying outbound->preferred->PriorityComputer logic was broken. Bumping this
to 100 peers cost another 14 seconds locally for the sub-test, so I made it pretty small.