Induce data availability into contract

[noel2004]

This PR make new contract work with data availability. The encoded tx data would be an argument when submitting block and being verified in the contract. As the result, the signature of submitBlock method has been revised.

For the new implement of submitBlock, some view function is added to facilitate debugging and checking everything is ready without wasting of gas fee.

Note current the original submitBlock method is still being kept in the contract under the name submitBlockLegacy in case we still need it for some legacy task or compare the gas usage. This need to be removed before the contract is officially released.

[noel2004]

Almost done for contract with data availability and handling L1 op (current only depositing and registering),
work left:

• Templatize the parameters in Operations
• When adding token, method should also specify precise of the token
• Update the dispatched amount in deposit event (should be scaled to the real amount used in exchange and rollup)

[noel2004]

For encoding the priority op of registry user, the gas usage increase to ~330k in registryUser method (before it cost ~90k)

[0xmountaintop]

can we combine shiftAndReverseBits16, shiftAndReverseBits32, shiftAndReverseBits64, shiftAndReverseBits128?

[noel2004]

tried but failed. If we defined both foo(uint16) and foo(uint32), the calling of foo seems to be considered as ambiguous even you have specified the type of argument explicitly.

[noel2004]

Finally all issues have been fixed and contracts now complete work with priority L1 ops. A script for depositing on L1 has also be induced