Migrate params to be self managed

[colin-axner]

Summary

Migrate all our on-chain params to be self managed, the SDK is removing x/param

See example pr

See upgrading docs

Ensure unset module params don't cause a panic on genesis export

The module will be removed after April 18th, 2023

Issues:

• Migrate 02-client params to be self managed #3500
• Migrate 03-connection params to be self managed #3501
• Migrate transfer params to be self managed #3502
• Migrate 27-interchain-accounts controller params to be self managed #3503
• Migrate 27-interchain-accounts host params to be self managed #3504
• Remove the deprecated parameter migration helper code #3621 Since there is no timeline for this yet, I'll remove it as requirement to close the epic issue.
• adapt connection e2e params test to use gov v1 message #3704
• adapt transfer e2e params tests to use gov v1 message #3705
• Add param e2es to compatibility tests.

---

For Admin Use

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

[crodriguezvega]

Looking at the PR for migrating x/mint it looks like we need to:

In tx.proto:

• Add an UpdateParams RPC endpoint to update params that receives a MsgUpdateParams and returns a MsgUpdateParamsResponse. Add the Msg service if needed.

In types/msgs.go:

• Implement sdk.Msg for MsgUpdateParams.

In keeper/msg_server.go:

• Implement RPC endpoint for UpdateParams.

In types/keys.go:

• Add key ParamsKey. This is the key that will be used to store the params.

In keeper/keeper.go:

• Add an authority field to the Keeper struct. This is the address capable of executing a MsgUpdateParams message, which will typically be the x/gov module account.
• Add getter function to Keeper type to return the authority.
• Remove paramSpace paramtypes.Subspace from Keeper struct.
• Add GetParams and SetParams functions .

Since NewKeeper takes an authority parameter (this is an API breaking change), we should adjust calls to pass in as authority authtypes.NewModuleAddress(govtypes.ModuleName).String().

And further:

• Create an exported/exported.go file that will be used for the migration and can be removed at a later release.
• Write migration function and expose it via the Migrator.
• Add a legacySubspace field to the Migrator.
• Create a types/params_legacy.go (this is also needed only for migration and can be removed later).

In types/params.go:

• Move any parameter store keys from params.go to params_legacy.go.
• Move ParamKeyTable and ParamSetPairs from params.go to params_legacy.go.

In module.go:

• Add a legacySubspace field in AppModule because it needs to be passed to the NewMigrator constructor function. This is an API breaking change.
• Bump the consensus version.

I believe we need to do this for:

• 02-client
• 03-connection
• transfer
• 27 host
• 27 controller

I guess we will need to adjust the existing tests setting params for 03-connection and transfer (this and this).

[crodriguezvega]

When working on this we need to update the documentation at the bottom here regarding adding a light client to the list of allowed clients via a param change governance proposal.

[damiannolan]

We should add an upgrade handler and e2e chain upgrade test for v7 -> v8 which performs the migrations and does some parameter lookups and assertions to make sure everything is set correctly.