feat: Upgrade SDK v0.47 to v0.50

[deepan95dev]

Related Github tickets

• Upgrading SDK v0.47.4 to v0.50.2

Background

This PR contains all the changes that has to be done for the upgrade, including integration tests/unit tests. This also contains latest master branch commits upto this

Testing completed

• keeper_integration_tests are moved to tests/integration/{module} with local fixture setup, leaving the dependency on app/app_setup.go (so the file app_setup.go is deleted)
• New test cases added are

• util/keeper/address_test.go which covers util/keeper/address.go
• /x/gravity/migrations/v1/migrate_test.go which covers /x/gravity/migrations/v1/migrate.go

• Most of the test coverage exists as it is with upgrade related changes, only few got updated as listed below

• tests/integration/evm/keeper/keeper_integration_test.go had putMessageInQueue in the case there is another upload valset already in only but later we needed to add for two more functions, TestFirstSnapshot_OnSnapshotBuilt() function and TestOldPublishedSnapshot_OnSnapshotBuilt function
• In x/paloma/ante.go after a series of discussion we arrived at the conclusion to use libmeta.getSigner but the test cases were failing so I mentioned here with comment, you may interpret this change to adapt with the test case.

• tested in a private testnet
• Upgrade testing is done

Breaking changes

• I have checked my code for breaking changes
• If there are breaking changes, there is a supporting migration.

[byte-bandit]

Blocking this until I find some time to step through all the changes. Other than code review, there's a few things missing here:

• Rebase on latest version of master
• PR description including short description & already performed tests
• before these changes are added to master, we need full E2E testing including compatibility with Paloma's side loading app Pigeon. We can compile a list of manual testing steps required to pass successfully before we consider going ahead.

[deepan95dev]

Blocking this until I find some time to step through all the changes. Other than code review, there's a few things missing here:

• Rebase on latest version of master
• PR description including short description & already performed tests
• before these changes are added to master, we need full E2E testing including compatibility with Paloma's side loading app Pigeon. We can compile a list of manual testing steps required to pass successfully before we consider going ahead.

How shall we proceed with E2E testing with Paloma's Pigeon App?

[byte-bandit]

How shall we proceed with E2E testing with Paloma's Pigeon App?

@taariq @verabehr @aleem1314

I suggest Volume compiles a list of manual testing steps and required proof of verification to share with the vitwit team. Happy to drive this on Notion until we settle on a run book.

[byte-bandit]

Some questions regarding proto changes.

[atheeshp]

1st round of feedback

[byte-bandit]

Only small stuff remaining, but most of it we'll just accept for now.

Can you please also run a full scan over the code base and make sure there's no other occurrances of CacheContext() that slipped through the renaming?

[byte-bandit]

Final review to @aleem1314

[aleem1314]

pre approving

[taariq]

@aleem1314 we have just TWO unresolved convos on the PR. We will merge on your check and resolve.

[faddat]

Just wanted to say that I thought this is cool :-)

[taariq]

Just wanted to say that I thought this is cool :-)

That means so much to us @faddat! Thank you!