Easier config generation for distributed bonder network

[shanefontaine]

Possibly this could mean re-thinking what the config looks like. Can we abstract it away entirely?

• Not a perfect comparison, but running Geth, for example, just requires me to download Geth and run the command geth and possibly some optional flags. Maybe we can get close to that.
• Current config generation and update is very manual (we generate and any updates we send them).

Ideally, a default covers almost everything (assuming they define their token and chains they want). Updates should be self-explanatory (mostly are now, IMO).

• Possibly define initial options (token, chains, rpc endpoints) in a start command
  • Possibly update with an update command (hop-node update config rpc --chain=polygon --endpoint='https://...'). I think we have this.
• Part of this could be removing some of the config options to simplify it. For example:
  • minThresholdAmount could be a default value based on the total stake (though this won’t matter in V2, I think)
    • routes can probably does not need to be defined in this format (probably just derived by the chains/tokens they define)