Problem: sdk v0.46.11 is not used

[yihuang]

Solution:

• update sdk/tendermint/ethermint dependencies
• patch cometbft-db to use grocksdb
• still need to replace tm-db because of indirect dependencies
• prepare v1.0.5 release in this PR.

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• Have you read the CONTRIBUTING.md?
• Does your PR follow the C4 patch requirements?
• Have you rebased your work on top of the latest master?
• Have you checked your code compiles? (make)
• Have you included tests for any non-trivial functionality?
• Have you checked your code passes the unit tests? (make test)
• Have you checked your code formatting is correct? (go fmt)
• Have you checked your basic code style is fine? (golangci-lint run)
• If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• If your changes affect the client infrastructure, have you run the integration test?
• If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

[mmsqe]

only date format need update

[yihuang]

only date format need update

yeah, fixed, thanks.

[calvinaco]

Checking Cosmos SDK v0.46.11 CHANGELOG
https://github.com/cosmos/cosmos-sdk/blob/v0.46.11/CHANGELOG.md

Want to check if this store change is potentially breaking or not?
cosmos/cosmos-sdk#14410

[yihuang]

Checking Cosmos SDK v0.46.11 CHANGELOG https://github.com/cosmos/cosmos-sdk/blob/v0.46.11/CHANGELOG.md

Want to check if this store change is potentially breaking or not? cosmos/cosmos-sdk#14410

should be non-breaking, we had the uneven case in some nodes before, which eventually manifested as app-hash mismatch, but not in the chain itself. in the future those cases (if ever happens again) will be revealed ealier.