Remove forward compatibility check

[pdrobnjak]

Describe your changes and provide context

#2377 this PR failed the forward compatibility check because of an ABI/API break, caused by changes in sei-protocol/sei-cosmos#605 more concretely codec/amino.go function renames.

The failure is not localised to #2377, the API break makes main broken from the perspective of CI/CD.

Analysis of pros and cons of this kind of compatibility check

Pro

When a Cosmos SDK version bump happens we will be compatible so the PR will most likely be a one liner dependency bump.

Con

Keeping forward compatibility works by random spilling over to the first person that creates the PR in the repo that has its forward compatibility broken.

Solution

Solution for now is to remove forward compatibility check altogether.

Correct way to check for forward compatibility would be to run this check in sei-cosmos (also it should be run for all repos dependent on sei-cosmos) so that the assignee is aware that he broke compatibility and should create subsequent PRs on dependent repos.

Testing performed to validate your change

CI run on this PR without the forward compatibility check.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.42%. Comparing base (b60dd14) to head (a98ec1c).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2395   +/-   ##
=======================================
  Coverage   60.42%   60.42%           
=======================================
  Files         314      314           
  Lines       31116    31116           
=======================================
  Hits        18801    18801           
  Misses      10994    10994           
  Partials     1321     1321           

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.