[dashboard] improve Gnosis Safe transaction handling

[kasparkallas]

What?

The transactions created by Gnosis Safe have synthetic transaction hashes (i.e. they're not real transactions on-chain until all the signers have signed) and the transaction tracking doesn't always work for this use-case.

For example, the transactions stay pending forever if they're not executed on-chain in the same app session.

Why?

Our biggest value customers are Gnosis Safe users and these issues strike out like a sore thumb. Especially in views with multiple one-after-another transactions like wrapping (allowance + wrap).

How?

• check if there are any new best practices when it comes to handling Gnosis Safe transactions
• old transactions should at least stop animating in the transaction drawer and be marked as stale

Other

Slack thread: https://superfluidhq.slack.com/archives/C066V4D00EA/p1708360686598469?thread_ts=1708354443.370179&cid=C066V4D00EA

[kasparkallas]

Added a few small fixes in the GDA PR:

• increased the pending TX expiration
• serialized the TX more securely