client: check node sync status

[tzemanovic]

We can leverage tendermint status method (https://docs.tendermint.com/master/rpc/#/Info/status) to print some stats about a node including whether it's synced or syncing to add e.g. anomac node-status command with optional --ledger-address arg, defaulting to the same value as for e.g. transaction and query CLI commands.

[cwgoes]

@bengtlofgren can you take this on (should be an easy one)?

[tzemanovic]

with the fix from #1182, where we stop committing genesis state in init-chain, we should also ensure that there is at least one block committed before proceeding with client commands - this can be a part of the same check

[tzemanovic]

with the fix from #1182, where we stop committing genesis state in init-chain, we should also ensure that there is at least one block committed before proceeding with client commands - this can be a part of the same check

Alternatively, we could re-do the init-chain to still commit to DB, which would mean that there's no issues with queries before the first block, but we'll need to ensure that it's not being committed twice. We might need to change the DB interface a bit for that or add some flag when it’s being committed that we could check during init-chain (as there is no block being created by it). Not sure if that's worth it as it's pretty minuscule improvement

[tzemanovic]

with the fix from #1182, where we stop committing genesis state in init-chain, we should also ensure that there is at least one block committed before proceeding with client commands - this can be a part of the same check

This one is causing some pain in e2e tests so I'll set this to higher prio. The current workaround is to wait for a first block before any queries and txs.