Automate genesis and config file generation

[nickray]

I think this can be simplified. Pull request coming as basis for discussion.

Three remarks:

• using the "name" as chain ID seems not such a good idea. For instance, gaia-3 is already pre-used, and if I guess the production chain name, I can "domain squat" it. Ideally, there would be a chain_id (might as well be a random ed25519 pubkey), and a chain_name.
• to me it's not clear how validator "power" and delegated coins in the "app with accounts" use case are connected. Is the initial power for bootstrapping consensus? Do genesis validators retain this power even if they turn out to be byzantine?
• ideally, if there is a loose coupling between genesis accounts and associated validators, there would be a signature involved from the account's key and the associated request(s) for validators.

[nickray]

@greg-szabo @adrianbrink