Predicate validation using the VM within the SDK

[digorithm]

Similar to dry runs.

[iqdecay]

• The changes proposed in feat: add a method to validate predicate transfers #1283 were actually not the ones needed.
• The point of doing predicates validation within the SDK, using the VM code, is to avoid having to do network calls (via dry-runs) to the node to validate predicates. This is with the idea that we are currently relying too much on the node for doing simple operations (estimations), thus putting extra and most likely superfluous computing power pressure on the node.
• The predicate validation should not only consider the predicate data (ie if the predicate returns true with the data it receives), but all of the elements that concur to the validation (or not) of the predicate. That implies correct gas estimation, the predicate or wallet having the necessary funds, inputs/outputs being set correctly, and possibly other conditions.
• This means that possibly there could be contract instructions needed to validate the predicate. In that case the VM within the SDK would maybe need to fetch some contract data from the node.