refactor: migrate store and api to CometBFT

[julienrbrt]

Description

ref: #14897, #14870

The goal of this PR is to migrate the Cosmos SDK modules that does not depend on the SDK to CometBFT.
Then a major version of these modules can be tagged, and the SDK can use it directly for its migration in #14897.
This will greatly limit the replace mess I was getting into.

Modules migrated here:

• api (by the mean of re-generating the proto and reverting anything outside ./api or ./store)
  • Note because the proto are as well committed, this will temporarily break make proto-gen on main, until the migration is completed (in refactor!: migrate Cosmos SDK to CometBFT #14897 thus).
• store

SimApp that was using a replace tag for store, now use a pseudo version to the latest from main (prior to the renaming).

TODO:
After #14904 is merged, replace it by Comet in this PR. It was done in that PR directly.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[tac0turtle]

utACK thanks.