Low - do a smoke test of read-only opportunities, though that's implied as part of this testing
What protocols, transaction types or contract interactions might be affected by this PR?
Testing
Connect a given set of EVM AccountIds (i.e a given wallet, or with the account management flags, a Ledger with certain accounts) or possibly none (Ledger with no EVM AccountIds connected)
Go to the earn page and ensure that zapper network requests are fired, and read-only opportunities are the ones for that specific set of accounts (or none and no requests, in case of no EVM accounts connected)
Switch to a different EVM AccountIds set (e.g connecting less or more EVM account numbers with the new Ledger flag, or switching wallets)
While still in the earn page, ensure that zapper network requests are fired again (assuming the new EVM accounts set is non-empty i.e you didn't disconnect all EVM accounts) and the new read-only opportunities are matching said EVM accounts set
Description
i.e finally makes
getAppsBalancesOutput
reactive on AccountIdsPull Request Type
Issue (if applicable)
closes https://github.com/shapeshift/web/issues/6872
Risk
Low - do a smoke test of read-only opportunities, though that's implied as part of this testing
Testing
Engineering
Operations
Screenshots (if applicable)
https://github.com/shapeshift/web/assets/17035424/8052e2e1-14c3-4332-8948-5aa9a9ae646e