feat: Handle benchmark and proof submission errors

[DamianPala]

When submitting a benchmark or proof, if a high transaction volume error occurs, the algorithm waits until a new block is mined before retrying. If a proof already submitted error occurs, the submission will not be repeated. Added more descriptive logs to enhance the clarity of the submission process.

[FiveMovesAhead]

In the revamp, this has been dealt with by re-queuing the benchmark/proof as long as the http error code is not 4xx