ICS loose ends

[sampocs]

Context and purpose of the change

This PR involves whitelisting missing param keys and a helper function for registering stToken denoms to consumer whitelist.
stTokens need to be whitelisted on consumer chain to be flown to provider chain and distributed to hub validators.
These updates were originally included into this PR but we pulled ICS updates from the PR for the convenience.

Brief Changelog

• Implement a function for registering stTokens as consumer rewards denom to the whitelist
• Add missing param keys to proposal whitelist
• Register stTokens to consumer reward denom whitelist automatically when new hostzones are added

Author's Checklist

• Run and PASSED locally all integration tests.

[mergify]

⚠️ The sha of the head commit of this PR conflicts with #860. Mergify cannot evaluate rules on this PR. ⚠️

[mergify]

⚠️ The sha of the head commit of this PR conflicts with #860. Mergify cannot evaluate rules on this PR. ⚠️

[asalzmann]

@strbrian can you add a more detailed description to this PR?

[strbrian]

@strbrian can you add a more detailed description to this PR?

Updated the PR description.

[asalzmann]

Looks good - we also discussed registering new denoms when a new host zone is added.

How are you thinking this will work?

[asalzmann]

lgtm! when we start dockernet, stuatom should now be registered as a fee denom - let's verify that as we test the upgrade

[strbrian]

lgtm! when we start dockernet, stuatom should now be registered as a fee denom - let's verify that as we test the upgrade

exactly, I actually already verified that as well.
once the dockernet is up, we can simply query consumer params using this link and check reward denom array.
http://localhost:1317/interchain_security/ccv/consumer/params