useBalance loads forever on a newly created wallet

[renra]

Describe the bug

A clear and concise description of what the bug is.

const { data, isLoading } = useBalance({ chainId: MyChainId, denom: MyDenom })

console.log(isLoading)

In case of a newly created wallet that has no balance, isLoading is always true which makes it look like the balance is loading forever where instead there's actually no balance.
...

To Reproduce

Steps to reproduce the behavior:

1. Create an app that connects a wallet and displays a balance using useBalance
2. Create a new wallet that has no coins
3. Connect the wallet

Expected behavior

isLoading becomes false to indicate the balance has been loaded. data can continue to be undefined to indicate there is no balance.

Temporary workaround

const { isLoading, data } = useBalances({ chainId: MyChainId, denom: MyDenom })

const balance = isLoading 
  ? undefined
  : (data && data.find((coin) => coin.denom === MyDenom)) || { denom: MyDenom, amount: '0' }
  
return {
  data: balance,
  isLoading
}

[steezeburger]

This reminds me of a similar issue I had with the stargate client

  // FIXME - no account here when the address does not have any native tokens for the chain?
  //  e.g. testing w/ Celestia Mocha-4 with an address that doesn't have any TIA on mocha.
  const account = await client.getAccount(sender);
  if (!account) {
    throw new Error("Failed to get account from Keplr wallet.");
  }

https://github.com/astriaorg/web-apps/blob/d190ce099b72d848515fbd07d97d475b0d575775/apps/flame-defi/app/features/cosmos-wallet/services/cosmos.ts#L19

I guess it makes sense. There is no record yet for that address on the chain. The question is, how do you determine a reasonable timeout to assume there is no balance vs some other network issue?