[GR-63033] [GR-63361] Add specialized filter primitive flow for constant y operand

[graalvmbot]

This PR introduces a specialized flow for primitive comparisons whose y(right) operand is a constant. I discovered that typeflow graphs for methods containing lost of if statements like

if(someBooleanMethod()){...}

tend to be hard to comprehend when debugging, because there are lots of use edges from a primitive constant 0 to primitive filters. Also, propagating the constant primitive typestate via use edges is essentially a waste of resources, because it is always the same value. I made a quick measurement and noticed that this pattern seems to be quite common. For example, on Spring Petclinic, almost 72% of primitive comparisons that we model in the analysis have constant y operands.

To sum up, this change should make the following improvements:

1. It makes typeflow graphs more compact and easier to understand.
2. It reduces the amount of use edges that always propagate the same constant value, which could improve analysis time and memory footprint, though I do not expect significant gains here.

As side tasks, this PR also:

• adds predicate-specific error messages to StrengthenGraphs to differentiate between optimizations caused by flows marked as disabled vs flows with empty typestate/list of callees
• introduces a verification for the fixed-point state of the analysis, useful to fail fast with a concrete counter-example if a flow ends up in an invalid state or an information between flows is not propagated correctly