Implement chain details lookup from RPC status endpoint or Cosmos Registry instead of requiring configs

[pharr117]

We can eliminate some of the required config values by looking up chain details using one (or both depending on what we want to pull in) of the following methods:

1. /status endpoint RPC - contains result.node_info.network showing the chain ID value
2. Chain Registry for the particular chain:
   • Contains bech32_prefix for the address prefix usable by message parsers
   • Subfolders do not match network name, we would need to most likely hit the RPC and get the chain subfolder by matching on the network name

Doing this will have some implications, mainly with what chain we store in the database. The database can contain multiple chains and we denote them using the network name.

We will then be able to eliminate the hard-coded config values for ChainID and account prefix from the [probe] block