Fix account balance discrepancies

[walmat]

Fixes APP-1689
Fixes APP-1564

What changed (plus any additional context for devs)

We had a couple issues going on here.

1. In the change wallet sheet we were using the addys account summary API to display balances, this was somehow really off.
2. On the wallet screen, we were filtering assets a little too heavily so the balance was different between BX and App.
3. In the send sheet I am now consuming the new method as well to keep it consistent

In order to solve both, we now consume a shared react-query hook in both places, which is the same one the BX uses.

Screen recordings / screenshots

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-08-05.at.16.49.58.mp4

What to test

[linear]

APP-1689 Issue: Balance Discrepancy between home and wallet switcher

[linear]

APP-1564 App displaying two separate balances on wallet switcher and home screen

[walmat]

separated all of the instances of invalidateQueries out because Arrays weren't working for whatever reason.

[walmat]

same here. Arrays were just not working..

[jinchung]

in the ControlPanel, AddressRow, and ContactRow, we have either the balance or show "No balance" - wondering about the loading state here as for now it'll just show "No balance" which can be jarring; at some point Matthew had something like a "Loading balance" copy placeholder, wonder if we want to use something like that

[jinchung]

just want to check:
for the useAddysSummary hook, isLoading will only be set to true at the initial load but will be false afterwards since we have keepPreviousData set to true which is great.

can we double check that we have something similar for the position queries, and that we aren't going back to isLoading set to true every time we're fetching after the initial fetch? we should check what we have configured for the positions data

otherwise would expect to result in something like profile balance showing up and then the row disappearing for a bit during a positions refresh, and coming back, etc. also while we're at it, generally check that the data is being refreshed in a reasonable manner now that we rely on this for balances instead of the underlying token data

[benisgold]

keepPreviousData is actually not used correctly there. react query actually "keeps previous data" all the time - even if data is stale, react query still provides it until the new data (fetched in the background) is ready to replace it. keepPreviousData keeps the previously fetched data when the query key changes, which is not behavior we want. i'm removing that.

but you're right that the useWalletBalances version of isLoading is somewhat problematic, for 2 reasons:

1. the addys query has a cache time of 24 hours while the positions queries do not have cache times
2. even if the cache times were the same may not be aligned, especially since these queries could be used in other contexts

this means that the problem you described would currently be valid every time a user cold starts the app since there is no positions query cache.

to mitigate it i've given all the queries in useWalletBalances a staleTime of 2 minutes and a cacheTime of 24 hours. this means worst case scenario isLoading will be true a few times a day, but in reality it will probably be fewer.

[jinchung]

🌮