0 - X --> X, if X is 0 or the minimum signed value
0 - X --> 0, if X is 0 or the minimum signed value and the sub is NSW
I noticed this pattern might be created in the backend after the change from D25485, so if I haven't flubbed the logic, we'll want to add a similar fold for the DAG.
I'm sort of concerned that calling computeKnownBits here could lead to compile-time performance problems, given that instsimplify is supposed to be inexpensive, and the condition is very unlikely to succeed in most code. I don't have any evidence it's actually an issue, though; maybe computeKnownBits is cheap enough that it doesn't matter.