Improve history updates.

[locutus2]

If a search failed low at an expected PV or CUT node do greater history updates.

STC:
LLR: 2.94 (-2.94,2.94) <-0.50,2.50>
Total: 95112 W: 24293 L: 23982 D: 46837
Ptnml(0-2): 285, 10893, 24906, 11170, 302
https://tests.stockfishchess.org/tests/view/6132aa1a2ffb3c36aceb926f

LTC:
LLR: 2.94 (-2.94,2.94) <0.50,3.50>
Total: 116352 W: 29450 L: 28975 D: 57927
Ptnml(0-2): 93, 12263, 32984, 12748, 88
https://tests.stockfishchess.org/tests/view/613394d12ffb3c36aceb92f4

Bench: 5348574

[snicolet]

@locutus2 congrats :-)

I have merged via c31fc8d despite the fact that Viz patch in e404a7d affects the same nodes (but Viz said it should be OK). If you feel there is a chance of overlap, feel free to test again. Another suggestion in the opposite direction would be to change the precondition in line 1325 to include also the cutNode flag there:

   // Bonus for prior countermove that caused the fail low
    else if (   (depth >= 3 || PvNode)
             && !priorCapture)

[locutus2]

@snicolet
On extends the search and the other update the histories. So I think too that there is no significant overlap despite triggereing at the same nodes. And your idea seems interresting. So a fail low at expected cut nodes would also considered.