Handle transaction versions with the QUERY_VERSION_BASE set

[kkovaacs]

cairo-lang has a feature called "query version", which is basically setting a bit flag in the transaction version field that means that the transaction must not be included in the chain.

The reasoning is that otherwise clients could not submit valid transactions (with a valid signature) for simulation/estimation that they don't (yet) want to be included on chain.

The flag bit is 2**128 (https://github.com/starkware-libs/cairo-lang/blob/c98fc0b50529185b7018208cb3460191eeb53e0d/src/starkware/starknet/definitions/constants.py#L63). If set, the sequencer rejects the transaction but otherwise it behaves in exactly the same way as if the bit was not set.

With current starknet-in-rust setting the flag results in validation errors (Unsupported version "340282366920938463463374607431768211458").

Please add support for this flag.

[juanbono]

Sure, we'll add support for this ASAP.

[kkovaacs]

Unfortunately this is still broken.

SUPPORTED_VERSIONS contains only QUERY_VERSION_BASE, which causes failures with v1/v2 transactions with the QUERY flag set (ie. version 0x100000000000000000000000000000001 or 0x100000000000000000000000000000002).