Run legacy param change proposals on main

[colin-axner]

Summary

With the change in #4730, key tables were only being registered in migrations. Given this and in comibination with a SDK version that doesn't safely handle panics in gov, it was possible for a legacy param change proposal to halt the chain due to unregistered key tables. While this will be fixed, we should run legacy param change proposals on main as well so we don't have to rely on manual discovery of these edge case issues

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged/assigned