SCORU: L2 node must watch number of ticks and messages

When processing messages, the L2 node must take care of respecting the limits on "Number of ticks" and "Number of message". Both are currently bounded integers.

One cannot produce a commitment for a piece of state if it the underlying PVM would consume more messages than allowed, or advances more ticks than allowed in respect to the previously staked state. This property is enforced by construction of the commitment data type (through fields of type Number_of_ticks.t and Number_of_messsages.t).

The interpreter in the L2 node that emulates the PVM behaviour in regards to message consumption and ticks must keep track of that. That means it must not be possible to produce PVM states that are not eligible for commitments.

Related: #2373 (closed)