Hook up minimum received and max sold values

[jinchung]

Fixes APP-1620

What changed (plus any additional context for devs)

Issues solved:

1. The minimum received value in the review panel was not hooked up correctly and always showed the same value as the output amount.
2. The minimum received value always displayed, even for output-based trades (which should show the maximum sold amount instead.)
3. Includes a version bump to swaps SDK v0.22.0

This PR will require some follow up after launch. We have a few updates that we want to do from the backend, so for now, the minimum received value is hooked up correctly (value after fees and slippage) but the maximum sold amount currently matches the input amount for output-based trades (the most pessimistic/conservative estimate we have.) We'll update this in a later release.

What to test

Test with a variety of input-based vs output-based trades.
Input-based trades should show "Minimum Received" in the review panel with a value that is less than the output amount.
Output-based trades should show "Maximum Sold" in the review panel with a value that matches in the input amount. (This will be updated later)

Screen recordings / screenshots

[linear]

APP-1620 Quoted output amount same as min received

[benisgold]

neither minimum received nor maximum sold appear to be working correctly. minimum received shows undefined as the amount, and maximum sold shows an incorrect amount that lacks formatting

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@rainbow-me/[email protected]	environment, eval, network	+11	3.4 MB	brunobar79

🚮 Removed packages: npm/@rainbow-me/[email protected]

View full report↗︎