feat: bump up cosmos sdk v0.50.x and cometbft v0.38.0

[dudong2]

Closes: #XXX

Description

Key dependency changes:

• Cosmos-SDK v0.45.9 to v0.50.6
• CometBFT (Tendermint) v0.34.25 to v0.38.6
• ibc-go v3.2.0 to v8.2.1
• go-ethereum v1.10.19 to v1.10.26

notable changed files

app/app.go
app/ante/ante.go
app/ante/handler_options.go
app/upgrades.go
encoding/config.go
server/start.go
server/util.go
rpc/backend/sign_tx.go
rpc/backend/node_info.go
rpc/namespaces/ethereum/eth/filters/api.go
rpc/namespaces/ethereum/eth/filters/filter_system.go
x/feemarket/types/msg.go
x/feemarket/keeper/keeper.go
x/feemarket/keeper/msg_server.go
x/feemarket/autocli.go
x/feemarket/module.go
x/evm/types/msg.go
x/evm/keeper/keeper.go
x/evm/keeper/msg_server.go
x/evm/autocli.go
x/evm/module.go
go.mod

app

• app.go
  • align the overall code with the structure of the cosmos-sdk's app.go, except for some parts related canto's modules and issue(ref. [Discussion] Policy Decision on BlockedAddrs in SDK v0.50 bump Canto-Network/Canto#122)
• ante
  • name change and few other structural changes related to authz.
• upgrades.go
  • add migration code due to upgrade of cosmos-sdk and ibc-go

rpc

• as go-ethereum versions go up, the implementation of funcs used internally may have changed

modules

• cli
  • remove legacy REST(ref. feat!: remove legacy REST  cosmos/cosmos-sdk#9594)
  • introduce autocli, so removes contents of tx.go, query.go
• msgs
  • move ValidateBasic logic to msg_server
  • remove funcs like Route, Type, GetSignBytes, GetSigners because they are supported by protobuf. But in case of MsgEthereumTx, GetSigners func is alive and implemented GetSignersFromMsgEthereumTxV2 func additionally.(ref. feat: bump up cosmos-sdk v0.50.x, cometbft v0.38.x Canto#53 (comment))
  • the module-specific proposal handler and param change was switched to msg level so authority has been added to the required module.(ref. Add CLI command to submit new Gov proposals, using Msgs cosmos/cosmos-sdk#10952)
• keeper
  • KVStore has been changed to use KVStoreService as opposed to the prev way of accessing KVStore via store key.(ref. refactor(x/staking)!: KVStoreService, return errors and use context.Context cosmos/cosmos-sdk#16324, ...)

NOTE

• as the versions of different modules in go.mod are upgraded, need to ensure that there are no security issues.

---

For contributor use:

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

---

For admin use:

• Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
• Reviewers assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[zsystm]

I leave some comments

[zsystm]

LGTM :)

[dongsam]

The review is still in progress, but let me leave part of what I discovered

• I think the sdk.AttributeKeyModuleand sdk.AttributeKeySender attributes of EventTypeMessage have been modified to emit automatically starting from sdk v0.47, as per the reference. It seems necessary to review and revise to ensure that this isn't leading to the duplicate emission of events. ( on msg_server.go )
• I've been keeping an eye on it as well, but it seems we need to ensure that any differences between versions 0.47 and 0.50 have been fully addressed.
• For the workflows that are failing before release, if there are items that don't need fixing, we should exclude them from the workflow. However, if they require fixing, it would be better to address those issues.