feat: import transactions from Safe builder

[gsteenkamp89]

Fixes #UMA-2431

motivation

We want users to be able to use the transaction builder in the safe app, export it, and then import it into the oSnap plugin.

How to test

1. create a new Proposal (check "use oSnap" checkbox)
2. Add a new transaction
3. Choose transaction type "Safe Import" from list
4. either drag n drop or select file from machine. (see 2 test files below)
5. there are multiple transactions in the file. choose 1 to import.
6. There are 2 transaction types Native transfer & contract interaction
7. The relevant input fileds should be populated with the values from the file and validated (it is possible to export invalid values from safe's builder, so we must validate each input here in the app)

Test files

This file works ✅
test-file-VALID.json

This file is corrupted ❌ (should display an error message)
test-file-INVALID.json

screenshots:

idle state

add file, choose transaction

Native transfer

Contract Interaction (includes erc20 transfers)

If you drag n drop a non-json file

If there is an error while attempting to parse the file. can be syntax errors in the file or the schema does not match what we expect.

[linear]

UMA-2431 figure out how to get safe transactions into snapshot osnap tx builder

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
snapshot	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 1, 2024 1:48pm
snapshot-goerli	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 1, 2024 1:48pm

[daywiss]

will defer reviewing this until changes from lee's suggestions

[daywiss]

still having an issue with deleting the first transaction in the list:

1. import valid tx file
2. remove first tx
3. see that first tx stays, but second tx is deleted

also should we disable this or let the user overwrite this tx with a new type:

[daywiss]

we need to allow multiple files

[gsteenkamp89]

we are only allowing them to drop 1 file at a time. but they can drop many, one after the other.

[daywiss]

this check should be done last. i think it should either be in this order, too short, too long, isBytesLIke

[gsteenkamp89]

fixed

[gsteenkamp89]

still having an issue with deleting the first transaction in the list:

1. import valid tx file
2. remove first tx
3. see that first tx stays, but second tx is deleted

also should we disable this or let the user overwrite this tx with a new type:

There was some funky localised state polluting things in this flow and causing bugs like this. Now only emitting state changes upstream, much better.

[daywiss]

looking good but found another issue. after quick fixing the issues in tx 1, and then trying to simulate, it still says its inavlid:

[daywiss]

looks good. remember dont merge this, please pr to snapshot!