Added retry logic to minaTransactionSender

[Raunaque97]

closes #340

• refactored minaTransactionSender to use a persistent Storage.
• added a simple retry Strategy to increase fees by a multiple and retry every few minutes if the transaction is not included.
• also handles the case if the sequencer restarts and the last sent transaction statuses were not updated in DB.

[rpanic]

So what I just discovered: When we setFee(), o1js erases all previous signatures in order for the tx to be signed again. And this makes sense - for the feepayer and some accountupdates, o1js uses the so-called "full commitment". This is simply just the hash of the whole transaction, including all accountupdates and the feepayer, whereas the non-full commitment would just the be hash of the current accountupdate.
Now, accountupdates can actually specify whether they want to use the full commitment or not (this is a field in the accountupdate struct that mina will receive as part of the transaction). And whatever commitment you choose, you signature or proof will only be valid given that exact commitment. it is kinda the basis on which you sign or prove. Now why is this important?
Signing or proving over a full commitment prevent replay attacks, like in other chains. But mina is a bit special, and unlike other chains, we sign a bunch of sub-parts individually. And so generally, in order to prevent somebody to rip out a part of our tx from the L1 mempool and replay it in their own specially-crafted malicious transaction and frontrun ours, we sign over the full commitment.
For resending transactions with a higher fee, this is a bit annoying - we don't want to re-prove the entire tx just because we changed the fee, right?
As I've mentioned above, luckily we can choose to opt-out of using the full commitment and use only the current accountupdate's commitment instead. But this is only possible in some distinct scenarios. My initial suspicious is that this is the case iff the accountupdate's validity is directly dependent on exclusively other full-commitment based accountupdates within the same transaction. But I'll have to think more on that definition.
Anyways, what we have to do before this PR will work without re-proving some accountupdates, is to use no full commitment generally. And for us to be able to do this, we need to examine the protocol and see if we can do this safely

[rpanic]

This is great! I have a few minor requests and questions, but I like it generally

[rpanic]

You forgot to create a migration for this new schema change - do this by cd-ing into the persistence pkg, then run prisma migrate dev and it'll you for a name and migrate

[rpanic]

Can you explain what this delay here accomplishes? I'd expect this function to only craft the new transaction and return it...

[Raunaque97]

This is used to add a delay between retries, like retrying a transaction every 5 minutes.

[rpanic]

I'm not against this schema, but I think for the reorg support we'll have to change this - but that will happen when we tackle that piece of work.

[rpanic]

What I'd love to see would be if we could add foreign-key out of settlement here. So in the Settlement entity, add a reference to the PendingTransaction so that we can establish that link

[rpanic]

As mentioned in the comment earlier, we need to figure something out to prevent re-proving