Max priority fee input overridden when handling incorrect base fee input error

[Lesigh-3100]

Bug Description

In TxHelpers, when we handle the error of an incorrect base fee, we override the max priority fee. This should, however, still use the max_priority input into the function.

Severity (High/Medium/Low)

Low

Steps to Reproduce

Run bot until base fee error - print the overridden max priority fee

Expected Behavior

max_priority input into the function should be used consistently

Actual Behavior

max_priority is overridden & can be doubled or more as a result

Impact Analysis (to be filled by contributors)

• Automated Tests: No tests that cover this.
• Risks:
• This should be isolated to TX submission.
• Performance: No
• Monitoring: No
• Logging: No
• Documentation: No