refactor: remove .Type() and .Route() from msgs (backport #14751)

[mergify]

This is an automatic backport of pull request #14751 done by Mergify.
Cherry-pick of 8dbdfea has failed:

On branch mergify/bp/release/v0.47.x/pr-14751
Your branch is up to date with 'origin/release/v0.47.x'.

You are currently cherry-picking commit 8dbdfea9e.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   baseapp/baseapp.go
	modified:   docs/docs/building-modules/02-messages-and-queries.md
	modified:   docs/docs/core/08-events.md
	modified:   testutil/testdata/tx.go
	modified:   types/simulation/types.go
	modified:   types/tx_msg.go
	modified:   types/tx_msg_test.go
	modified:   x/auth/migrations/legacytx/stdsign.go
	modified:   x/auth/types/msgs.go
	modified:   x/auth/vesting/types/msgs.go
	modified:   x/authz/msgs.go
	modified:   x/authz/simulation/operations_test.go
	modified:   x/bank/simulation/operations.go
	modified:   x/bank/simulation/operations_test.go
	modified:   x/bank/types/msgs.go
	modified:   x/bank/types/msgs_test.go
	modified:   x/consensus/types/msgs.go
	modified:   x/crisis/types/msgs.go
	modified:   x/distribution/simulation/operations.go
	modified:   x/distribution/simulation/operations_test.go
	modified:   x/evidence/types/genesis_test.go
	modified:   x/feegrant/msgs.go
	modified:   x/feegrant/simulation/operations.go
	modified:   x/feegrant/simulation/operations_test.go
	modified:   x/gov/types/v1beta1/msgs.go
	modified:   x/group/msgs.go
	modified:   x/group/msgs_test.go
	modified:   x/group/simulation/operations.go
	modified:   x/group/simulation/operations_test.go
	modified:   x/mint/types/msgs.go
	modified:   x/simulation/event_stats.go
	modified:   x/simulation/util.go
	modified:   x/slashing/simulation/operations.go
	modified:   x/slashing/simulation/operations_test.go
	modified:   x/slashing/types/msg.go
	modified:   x/staking/keeper/msg_server.go
	modified:   x/staking/simulation/operations.go
	modified:   x/staking/types/msg.go
	modified:   x/upgrade/types/msgs.go
	modified:   x/upgrade/types/msgs_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   CHANGELOG.md
	both modified:   x/distribution/types/msg.go
	both modified:   x/evidence/types/msgs.go
	both modified:   x/gov/client/utils/query_test.go
	both modified:   x/gov/simulation/operations.go
	both modified:   x/gov/simulation/operations_test.go
	both modified:   x/gov/types/v1/msgs.go
	both modified:   x/staking/simulation/operations_test.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[tac0turtle]

this seems api breaking for testing. @julienrbrt i saw you tagged as backport to 0.47.1. is there good reasoning to do it here?

[julienrbrt]

There should not be any behavior change, actually. We update our tests, and clean-up the code.
I don't think it is breaking (route() and type() were always the msg urls), moreover, chains on v0.47 won't use Route() and Type(). So it is an improvement on simulations.

[tac0turtle]

hmm, its api breaking in the sense that it requires users to upgrade code instead of using a newer version and releasing, or does a user not need to make these changes?. I dont see much benefit to backporting this. Are you fine with closing if the above lines are required

[julienrbrt]

No, a user does not need to make these changes. However, I do agree what apart from cleaning up, it isn't needed.
So let's close, v0.48 will be cleaner.

[github-advanced-security]

You have successfully added a new gosec configuration .github/workflows/gosec.yml:Gosec. As part of the setup process, we have scanned this repository and found 229 existing alerts. Please check the repository Security tab to see all alerts.