PR consists of 2 improvements on nodes with excludeMove:
1. Remove xoring the posKey with make_key(excludedMove)
Since we never call tte->save anymore with excludedMove, the unique left purpose of the xoring was to avoid a TT hit. Nevertheless on a normal bench run this produced ~25 false positives (key collisions) To avoid that we now forbid early TT cutoff's with excludeMove Maybe these accesses to TT with xored key caused useless misses in the CPU caches (L1, L2 ...) Now doing the probe with the same key as the enclosing search does, should hit the CPU cache.
2. Don't probe Tablebases with excludedMove.
This can't be tested on fishtest, but it's obvious that tablebases don't deliver any information about suboptimal moves.
Side note: Very surprisingly it looks like we cannot use static eval's from TT since they slightly differ over time due to changing optimism. Attempts to use static eval's from TT did loose about 13 ELO. This is something about to investigate.
