fix(tron-wallet-snap): distinguish inactive accounts from HTTP failures on fetchAssetsAndBalancesForAccount

[ulissesferreira]

Summary

• Follow-up to Stanley's review on feat(tron-wallet-snap): add CoreAssetsAdapter and mapControllerAsset #144: inspect Promise.allSettled rejection reason in CoreAssetsAdapter.fetchAssetsAndBalancesForAccount.
• Treat only TrongridAccountNotFoundError as an inactive account; rethrow HTTP and other unexpected failures from account info, resources, and staking rewards instead of reporting zero balances.

Test plan

• Confirm inactive accounts (TrongridAccountNotFoundError) still return zero snap-owned assets
• Confirm a TrongridHttpError from account info fails the fetch instead of looking like an inactive account
• Confirm HTTP failures from getAccountResources / getReward also fail the fetch
• yarn workspace @metamask/tron-wallet-snap run test (or check-tron)

[stanleyyconsensys]

thx for the work, Looks great to me

i assume you already have some place to catch and trace the error

just question, since u dont throw error when acc is not found,
can we assume addressResourcesRequest and addressStakingRewardsRequest will not throw error if account not found?

[ulissesferreira]

thx for the work, Looks great to me

i assume you already have some place to catch and trace the error

just question, since u dont throw error when acc is not found, can we assume addressResourcesRequest and addressStakingRewardsRequest will not throw error if account not found?

Yes we can, they basically just return empty