Fix for the bug in the implementation of evalCall() for constructors.
The StmtNodeBuilder created isn't actually used during runCheckersForEvalCall(). A new builder is used instead, inside runCheckersForEvalCall(). So NodeBuilder believes that no transitions were added inside runCheckersForEvalCall(), and therefore the analysis must continue from the predecessor node. And it was causing the exploded graph branching in evalCall for a constructor.
Fixing it by passing the NodeBuilder to runCheckersForEvalCall() and use it instead of new NodeBuilder
We should probably delete the copy-constructor for node builders. I've no idea what it's supposed to do anyway and the whole problem that we're having here is due to there being too many of them already.