This patch fixes the issue noticed in D54532. The problem is that `cst_pred_ty`-based matchers like `m_Zero()` currently do not match scalar undefs (as expected), but *do* match vector undefs. This may lead to optimization inconsistencies in rare cases.
There is only one existing test for which output changes, revert the change from D53205. The reason here is that vector `fsub undef, %x` is no longer matched as an `m_FNeg()`. While I think that the new output is technically worse than the previous one, it is consistent with scalar, and I don't think it's really important either way (generally that undef should have been folded away prior to reassociation.)
I've also added another test case for this issue based on InstructionSimplify. It took some effort to find that one, as in most cases undef folds are either checked first -- and in the cases where they aren't it usually happens to not make a difference in the end. This is the only case I was able to come up with. Prior to this patch the test case simplified to `undef` in the scalar case, but `zeroinitializer` in the vector case.