Fix date displayed with no Tx

[Tbaut]

closes #430

This was more complex than expected. The problem was related to a race condition between

• getting the pending TX from the chain (querying the multisig storage)
• getting the call data info from the chain (involving querying older blocks and get the calldata from the asMulti calls)

The second call can take time, and when changing accounts, a reset wouldn't be performed. Now since Promises can't be stopped, this resulted in the second promise resolving with outdated data. I solved it in making the 2 calls sequential and less dynamic. It's not really an issue since they should strictly follow each other. I've been consolidating all this logic which used to be separated, into the usePendinTx hook. It's a lot, but it should be more comprehensible already.

To see the bug, you'd have to:

• have many pending TXs (I had 10) and at least 1 from the multisig (as opposed to from the proxy). You can try by watching 5EMm18Z8WWWT2wit1RxpoZv39goPdYmSksnDTePYAzrUhdJv on Rococo.
• then you should select the account with the many tx in the UI, wait for them to show, and switch to an account that doesn't have any pending tx. --> you'd see the date with no tx.

---

Submission checklist:

Compatibility

• Functionality of change validated with a connected account with multisig
• Applicable elements hidden / disabled for watched multisigs / pure
• Looks good for solo multisig
• Looks good for multisig with proxy

[asnaith]

Nice! The fix works successfully, I can no longer recreate the issue on this branch

[Lykhoyda]

@Tbaut looks good! I pushed the PR where I replaced the old AggregatedData with the new interface CallDataInfoFromChain. As I had errors during the build. Please confirm if it's correct

[Tbaut]

Thanks for the review. I'll merge this PR next week as it's touching quite some critical logic, and I'm not very available in the next days if something goes wrong.