chore: clean-up of #15151

[julienrbrt]

Description

Some clean-up of #15151. Noticed them while backporting in #15218

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[julienrbrt]

This is said on the message itself.

[tac0turtle]

thanks, if someone is migrating from v4 -> v5 they will not have the values set out in the migration in v5, how is this handled?

[julienrbrt]

thanks, if someone is migrating from v4 -> v5 they will not have the values set out in the migration in v5, how is this handled?

It is handled in migration v4 during the params migration (which happened in v0.47).
In v0.48 we only include expedited proposal and cancelling proposal, so that is only what should be there.

[julienrbrt]

You've made me notice proposal cancel parameter were not set in v5 migration however.