feat: manage relayer tasks

[wanglonghong]

Description

Type of change

• Docs change / dependency upgrade
• Configuration / tooling changes
• Refactoring
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)

Fixes

Related pull request(s)

[sanchaymittal]

will wait for preetham's approval to for above

[sanchaymittal]

@preethamr waiting for your review

[preethamr]

What would be the impact on performance ?

[wanglonghong]

What would be the impact on performance ?

Once the task is sent to gelato, it just removes messages from pending list and nonce also increases.
In worst case(out of funds), the task can fail on gelato's end but that batch messages will never picked up because it has been already removed and don't re-add it to pending list

[preethamr]

In worst case(out of funds), the task can fail on gelato's end but that batch messages will never picked up because it has been already removed and don't re-add it to pending list

This is a possible scenario right ? How would we then retry ?

[wanglonghong]

How would we then retry ?

1. We don't remove the batch from the pending list but we update its status to sent.
2. In each run, it tries to get the task status thought gelato api.
3. If Cancelled, it updates the statuses to nonce which means it can be picked up again by lighthouse-prover-pub.
4. If ExecSuccess, it removes the batch from pending,