Also search null move in QS iteration of deeper nodes
The QS iteration of deeper nodes is intended to replace sorting
the captures in front of the 1-ply iteration. Not to generate an actual
QS result. It is thus not a good idea to stand pat or take a stand-pat
cutoff in this iteration, as this could mean we start the ply-1 iteration
blindly (and thus likely with pointless non-captures) if null-move turns
out to be worse than stand-pat (failing low) because of a threat.
So we now do null move not based on iteration number, but based on
total node depth. Except that in the pre-QS iteration it is still suppressed.