feat: ADR-040: Implement BadgerDB backend

[roysc]

Description

Partially resolves: vulcanize#14

Implements a BadgerDB-based backend for the DB interface introduced by #9573 and specified by ADR-040. This uses Badger's "managed" mode for version management, and supports optimistically concurrent transactions (required one patch upstream to fix handling of write conflicts).

---

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 - n/a
• 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)

[roysc]

As this depends on #9573, I'm making it a draft for now and will rebase when that is merged.

Also, not sure if more documentation is needed beyond godoc comments.

[alexanderbez]

I'm going to wait until the mem-db PR is reviewed and merged before reviewing RocksDB and BadgerDB variants. We can rebase on master after it's merged.

[tac0turtle]

@roysc can this be rebased. Then we can begin reviewing

[roysc]

Rebased and ready for review

[roysc]

Along with review follow-ups, I fixed the version manager initialization so it's not dependent on ordered input, and updated a test case to verify its behavior.

[tac0turtle]

utACK

[tac0turtle]

@roysc could you update to master, this will allow the bot to merge the PR

[alexanderbez]

We can merge this, yes?

[orijbot]

Visit https://dashboard.github.orijtech.com?back=0&pr=9848&remote=false&repo=cosmos%2Fcosmos-sdk to see benchmark details.