fix: increase minFeePadding in e2e_bot bridge resume tests

[AztecBot]

Summary

Fixes flaky e2e_bot test failure on merge-train/spartan caused by gas fee escalation beyond the 10x padding.

• The does not reuse prior bridge claims if recipient address changes test was failing because gas fees rose ~13.4x between fee estimation and transaction processing
• The previous minFeePadding: 9 (10x multiplier) added in chore: increase max fee bots use in tests #20867 was insufficient for this test, which builds many blocks due to bridge operations from earlier tests plus its own additional bridge claim
• Increased minFeePadding from 9 to 99 (100x) for both bridge resume tests to handle worst-case fee volatility

Error: maxFeesPerGas.feePerL2Gas must be greater than or equal to gasFees.feePerL2Gas, but got maxFeesPerGas.feePerL2Gas=698400000 and gasFees.feePerL2Gas=932800000

Test plan

• Change is purely numeric (9 → 99) in test config, no compilation risk
• CI will verify the test passes with the increased padding

ClaudeBox log