tdb2 has various places where it recovers from failure (eg. falling
back when it can't open /dev/urandom, or allocation for error
logging). We want to test those paths, but doing so thoroughly causes
cominatorial explosion.
Add FAIL_PROBE for such cases: in this case it goes only 3 more calls
deep.