fix(rollup-relayer): better handle commit batch revert

[colinlyguo]

Purpose or design rationale of this PR

Problem:
When rollup-relayer encounters a batch commit failure, it continues to commit subsequent batches, which would fail.

Solutions:

1. Before committing a new batch, check If the parent batch has failed, if so, stop.
2. Use estimateGas for batches that have been committed failed.

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• fix: A bug fix

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

• No, this PR doesn't involve a new deployment, git tag, docker image tag
• Yes

Breaking change label

Does this PR have the breaking-change label?

• No, this PR is not a breaking change
• Yes

[codecov]

Codecov Report

Merging #981 (27b57af) into develop (caa16e1) will decrease coverage by 0.05%.
The diff coverage is 26.66%.

@@             Coverage Diff             @@
##           develop     #981      +/-   ##
===========================================
- Coverage    48.19%   48.14%   -0.05%     
===========================================
  Files          100      100              
  Lines        10580    10590      +10     
===========================================
  Hits          5099     5099              
- Misses        5060     5069       +9     
- Partials       421      422       +1     

Flag	Coverage Δ
rollup	66.33% <26.66%> (-0.22%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
rollup/internal/orm/batch.go	56.80% <66.66%> (ø)
rollup/internal/controller/relayer/l2_relayer.go	40.72% <16.66%> (-0.84%)	⬇️

[0xmountaintop]

just a nickpit