fix: add amountOutMin to longtail

[0xApotheosis]

Description

Adds a amountOutMin value to the first "step" of a longtail to L1 swap (the call to the swapIn function of the UniswapV3 contract on Ethererum).

This PR also re-enables longtail to L1 swaps. - keeping this off for now. There is an unrelated issue that seems to be showing an incorrect value in the trade confirm step. I'm not yet sure if this is a longtail thing, or a multi-hop wiring thing. I'll investigate and fix in a follow-up PR.

Note, as a follow-up we'll need to align with @shapeshift/product on how to handle slippage on trades with multiple steps.
A longtail to L1 swap has two steps, each with the slippage value encoded. This means that if a user has selected 1% slippage, it's possible both steps could incur that entire slippage amount, resulting in a total slippage of 1.98% for the trade.

An example TX performed on this branch:

• https://etherscan.io/tx/0x9c77ba83ef7281e9ea82bc6fb2f5a1de80708e62c2a09befb21720703423a038
• https://viewblock.io/thorchain/tx/9c77ba83ef7281e9ea82bc6fb2f5a1de80708e62c2a09befb21720703423a038

Pull Request Type

• 🐛 Bug fix (Non-breaking Change: Fixes an issue)
• 🛠️ Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
• 💅 New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

Contributes to #6017

Risk

High Risk PRs Require 2 approvals

High - an incorrect implementation could leave users open to sandwich attacks.

Testing

Perform a longtail to L1 swap (e.g. CRV on Ethereum to DOGE). Ensure that the specified slippage value is correctly encoded in both the amountOutMin of the Ethereum TX:

and on the associated THORChain TX (in the memo):

Engineering

☝️

Operations

☝️

Screenshots (if applicable)

[gomesalexandre]

Stamping as this does what it says from a functional perspective, a few comments that are not related to the functionality of this.

Tested locally:

Quote

Debugged expectedAmountOut and amountOutMin looks sane

On-chain amountOutMin is present and sane

Tx Success detection

@0xApotheosis while this was (most likely not?) introduced by this PR, I noticed a discrepancy in the final amount received that's shown here - a discrepancy from the quote, which itself is very close (although not 100% accurate) to the actual on-chain received amount

i.e:

• ~0.527 ATOM on our success status step vs. ~0.422 on quote 🚫
• ~0.422 ATOM on our quote step vs. ~0.421 ATOM on-chain ✅

[0xApotheosis]

Thank @gomesalexandre. I think something related to the multi-hop UI is broken here, as that success status step is off (it seems to show the amount before fees).

I'm not sure if it only affects longtail swaps, or all swaps, but I'll update this PR to not turn on the longtail feature flag in production until I work out what's up and PR a fix.