Better error messages when node isn't synced

[jackzampolin]

When a node isn't synced it can give confusing/misleading errors:

$ gaiacli query account cosmos1s6esgd037n3hurdyhn73yq0ze9cxutymxsvnh0  \
  --indent --chain-id foo --node=127.0.0.1:26657
ERROR: {"codespace":"sdk","code":1,"message":"substore proof was nil/empty when it should never be"}

$ gaiacli query account cosmos1s6esgd037n3hurdyhn73yq0ze9cxutymxsvnh0  \
  --indent --chain-id foo --node=127.0.0.1:26657
ERROR: Validator set is different. Got AB54FD93489D5CC4E51064402B3603ECD59038A016E17E67080E6CBAA27CAF8D want 161972152783A1F1A566A2C3A67F30162C4AC16AD29720259A6DC66A27FF0A8C

$ gaiacli query account cosmos1s6esgd037n3hurdyhn73yq0ze9cxutymxsvnh0  \
  --indent --chain-id foo --node=127.0.0.1:26657
ERROR: Invalid commit -- insufficient old voting power: got 0, needed 7

One way to mitigate this would be to check if the node is synced using the /status endpoint and then tailor the error to the sync status of the node. Another option would be to add your node may be syncing, please check /status message.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[likhita-809]

@marbar3778 do you think this fix 418a335 works here ?

[fig666]

message me after command is over for usage again, in the meantime the process of merging and modification and external remote usage is prohibited. i hope you comply

[likhita-809]

does this seem better now 46f2b2d @marbar3778 ?

[tac0turtle]

looks good to me