Add tuple support to SafeSnap

[auryn-macmillan]

Is your feature request related to a problem? Please describe.
SafeSnap currently does not support importing tuple as a parameter from json files.

Describe the solution you'd like
We should be able to pass a tuple parameter in as a json array.

[
"0x49535f52454c41595f56414c4944000000000000000000000000000000000000",
"1650814318",
"0x72656c6179486173683a373961316436376330326336376430663637643936343335323066396566336261303330653639643238373637303934343363383261316439633664656238342c6f6f5265717565737465723a37333535656663363361653733316635383433383061393833383239326337303436633165343333"
]

[zzuziak]

@mktcode what's the status of this issue?

[mktcode]

This is fixed in the new Safesnap implementation. It supports infinity nested data of all types, though a contract has a stack limit of course but the transaction builder won't be a limiting factor anymore. In the current version UMA has just been integrated now and we can now discuss now how to go forward from here.