Getting all the data from chain.json about cosmos-omnibus

[tombeynon]

We can definitely pull more runtime config from chain.json, does it make sense to use fixed_min_gas_price if available for the minimum_gas_price? Would be great to automate that particular config since Osmosis will require it soon.

Buiild time config is something I've thought about making entirely dynamic from chain.json but I think it breaks the Docker convention of repeatable builds - it would be very easy for a chain to be accidentally upgraded/downgraded when a new version of Omnibus is released for example. I was thinking a Makefile/CLI tool for Omnibus might be a good idea though - it could automate the addition/update of chains using a chain.json, which would update the build.yml files with the correct version, binary URL etc.

I'd love to get to a place where changes to the Chain Registry can automatically trigger updates in Omnibus, probably with a PR review in the middle.

[boz]

We can start optionally using chain.json at build time to set defaults, not a bad idea.

You can use chain.json for configuration at runtime - but it doesn't look like we're pulling gas prices at the moment. Runtime configuration can also be set manually via environment variables or flags.

[tombeynon]

Fixed in #154 and #162