fix: remove addSlippageToMemo in favor of addLimitToMemo

[NeOMakinG]

Description

• I removed addSlippageToMemo because the only thing it does is taking the slippage out of the limit and putting it back, the role of putting it in the memo should be limited to addLimitToMemo and this limit should be precalculated
• To calculate the limit I used a util getLimitWithManualSlippage then I finally used addLimitToMemo

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)

partially #6777

Risk

High as it might add wrong behaviors to minAmountOut of THORChain memos

Testing

Memos and particularly minAmounOut part should be the same as before:
Tests those swaps and compare the minAmountOut values in the memos by adding console logs in getL1quote in every handlers:

• BTC => ETH
• BTC => BCH
• ETH => RUNE
• ETH => COSMOS
• SHIBA => BTC
• DOGE => ETH

Engineering

n/a

Operations

n/a

Screenshots (if applicable)

Rune => BTC

Amount before: 34217, after slippage: 33874, seems good as it represent 1%

ETH => COSMOS

Amount before: 464163000, after slippage: 459521370, seems good as it represent 1%

SHIB => BTC

Amount before: 45308, after slippage: 44854, seems good as it represent 1%

[gomesalexandre]

Spot-on! Much cleaner that way and implementation is sane (code moved around).

Confirmed at runtime with 10x dev console.logs limit is still happy i.e 498441*90/100 = 448596.9, and limit is indeed 448596