Sanity Checker: store/load Arguments

[anton-trunov]

Summary
Some kind of interval analysis for bit-width arguments would be nice to have, although the most frequent case is by far when it's just an integer literal or a constant.

Context
A frequent case is when due to a typo people put incorrect amount for bit width of some date they store in a builder or parse from a slice. For instance, I've seen contracts with an attempt to store 0 bits.

Some functions from @stdlib/std/cells.tact:

• storeInt(self: Builder, value: Int, bits: Int) must have its 3d argument bits to be in the range [1; 257];
• storeUint(self: Builder, value: Int, bits: Int) must have its 3d argument bits to be in the range [1; 256];
• loadBits(self: Slice, l: Int) must have the l argument to be at least non-zero;

Examples

fun send(params: SendParameters) {
    let b: Builder = beginCell();
    b = b.storeInt(1, 0);
    ...
}

Use instead:

fun send(params: SendParameters) {
    let b: Builder = beginCell();
    b = b.storeInt(1, <non-zero-amount-of-bits>);
    ...
}

[jubnzv]

It looks useful to have. I think the linter should support only a specified set of the Func standard library functions and process all the native Tact functions that are aliased to them.

[jubnzv]

Related to the implementation of #20.

Another related issue: what if the user is trying to store a reference to the same cell multiple times?