feat: thorchain use max_streaming_quantity quantity in memos

[gomesalexandre]

Description

See #5733 (comment) for reference - this tackles part of our problem by ensuring our streaming quantity conforms to the one returned by the quote as max_streaming_quantity.
This does not yet tackle the issue of 0 limit memos returned by THOR we then ignore and set our own limit instead.

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)

• tackles THORSwap trades refunded at "Emit asset is less than price limit" #5733

Risk

• At worst, this should come as no change to our current logic, as 0 indicates let the network decide the best streaming quantity. Meaning that would be explicit instead of implicit here, but the actual limit used by THOR would be the same
• At best, using an explicit quantity would make some current failing trades go through, if the 0 limit doesn't automagically work as it should

Testing

• do a streaming swap and ensure it is still going through

Engineering

• Ensure the interval we use for streaming swaps is the one we're getting from the quote as max_streaming_interval

Operations

Screenshots (if applicable)

Tested with two pairs/amounts as the quantity may differ depending on the pairs/amounts

10,000 USDT -> DAI

• Develop - 0 quantity

• This diff - 53 streaming quantity

0.08 BTC -> DOGE

• Develop - 0 quantity

• This diff - 2 quantity

[gomesalexandre]

Current dependencies on/for this PR:

• develop
  • PR feat: thorchain use max_streaming_quantity quantity in memos #5734 👈

This stack of pull requests is managed by Graphite.

[gomesalexandre]

Closing in favor of #5748 - we may want to re-add explicit swap quantity in the future if we decide to expose memos to the user, but for now let's roll with the good ol' if it ain't broken don't fix it