Improve gas amount derivation for 'squidRouterPay' phase

Context

It sometimes happens that Vortex is charging the squidrouter transaction for onramps with not enough gas. It's not clear why it's not enough as the squidRouterPay phase is actually getting the gas information directly from the axelar endpoint, but there has to be something we are missing.

In cases where not enough was charged by Vortex, manually adding the gas in the Axelar UI works. This means, the Axelar UI has the right means to derive the missing gas amount. The following code links should help understand how they derive the exact gas required in their UI.

• The implementation of the function that is called when clicking on the 'Add gas' button is here.
• That implementation is using a class from their axelarjs-sdk, namely the AxelarGMPRecoveryApi

TODO

Look through the code and adjust the logic of the squidRouterPay phase to use a similar derivation for the required gas.

Start with the squidRouterPay phase and compare its gas derivation with the Axelar UI implementation in GMP.jsx and AxelarGMPRecoveryAPI.ts. Trace how the phase obtains gas from the Axelar endpoint, then confirm that it derives the required amount consistently with the linked recovery API so the Axelar UI does not require additional gas.