fuzzer: Verification state not properly updated for default null cases

[peterenescu]

Description

Fuzzer may fail for what appears to be a simple behavioral mismatch, but it's slightly more complicated than that. The difference comes from how Velox and Presto handle nulls. For the former, Velox may not always throw as long as some other column is null. As an example,

presto> presto:di> select SMALLINT '10515' * SMALLINT '12543';
Query 20250305_181421_00003_nqej6 failed: smallint multiplication overflow: 10515 * 12543

This should fail for the reason above; however, the following may not if any column is null:

presto> multiply("c0",floor(divide("c1",plus("c2",abs(negate(divide("c3",plus(multiply(10515,12543),try_cast yow("c4") as SMALLINT))))))))

This may confuse the fuzzer, but we don't want to register this as a difference without first confirming Velox didn't throw not because of default null behavior.

This behavior will have to be updated in the Verifier and already the skeleton is there, but will need some fine-tuning.