feat : upgraded the app with evm module to SDK v0.50

[vishal-kanna]

No description provided.

[aleem1314]

Here are few things we have to do after fixing errors in each module

• Params are deprecated. Move params to module state Ref.
• Update module to use collections
• Add AutoCLI support

[aleem1314]

Update this branch with v0.50.0-upgrade and revert all logger changes

[akhilkumarpilli]

Still there are few things need to be updated:

• Add signer field proto annotation, remove GetSigners and GetSignBytes implementations in every sdk.Msg defined in this module.
• Add EndBlocker, BeginBlocker and other compiler assertions (if required any) in module.go.
• Update Endblocker method structure to new SDK defined type if there are not validator updates involved in it.
• Update BeginBlocker method structure.

Please go through migration docs much deeper and update any if still not updated.

[akhilkumarpilli]

Why these values are nil? Remove these fields if not needed or add TODO comment if they need to be updated later.

[byte-bandit]

Still there are few things need to be updated:

• Add signer field proto annotation, remove GetSigners and GetSignBytes implementations in every sdk.Msg defined in this module.

Warning

Paloma is using a custom signer function using an embedded Metadata field on every message. There's a custom Ante handler responsible for parsing and verifying signatures on messages. This should stay as is and not be touched. GetSigners and GetSignBytes should be handled by libmeta on every message, but they need to stay implemented for this to work.

[byte-bandit]

@aleem1314 @vishal-kanna

Please start using liblog.FromSDKLogger(k.Logger(SdkCtx) in the future. There are still ocurrances here without.