Centralize some of the consensus timing config fields.

[SpicyLemon]

Summary

There's several consensus timing fields in the config file (in config.toml) that we'd like to standardize across nodes.

Problem Definition

We see a lot of sporadic block times and it's possibly related to various consensus. settings which each node can define for itself.

Proposal

There's a couple things we can do depending on how much effort we want to put in.

1. (low effort) Hard-code the values in our config management stuff. This will involve providing the hard-coded values to viper.
2. (more effort) Create some new params to hold them and store them somewhere. Set them in the next upgrade, and provide endpoints for getting and setting-via-gov-prop.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned