chore: Db linting (#12141)

* mainly sdk.int to cosmossdk.io/math

* staking keys

* fumpt

* var-naming linter errors and a fumpt

* Update CHANGELOG.md

* Update .golangci.yml

* Update CHANGELOG.md

* Update test_helpers.go

* Update test_helpers.go

* fumpt and lint

* this lints the db module, and makes it easier to use.  It adds breaking name changes

* DBConnection -> Connection

* previous commit contained a merge error

* Update test_helpers.go

* Update test_helpers.go

* db renamings

* merge master

* changelog

* DBWriter -> Writer

* consistent multistore reciever

* standard recievers for multistore v2alpha1

* general cleanup of linting issues

* more linter fixes

* remove prealloc linter

* nolint the secp256k1 import

* nolint the secp256k1 package

* completenolint resulting in a diff that has only nolints

docs/core/store.md

@@ -249,7 +249,7 @@ An interface providing only the basic CRUD functionality (`Get`, `Set`, `Has`, a
 This is the new interface (or, set of interfaces) for the main client store, replacing the role of `store/types.MultiStore` (v1). There are a few significant differences in behavior compared with v1:
 
 * Commits are atomic and are performed on the entire store state; individual substores cannot be committed separately and cannot have different version numbers.
-* The store's current version and version history track that of the backing `db.DBConnection`. Past versions are accessible read-only.
+* The store's current version and version history track that of the backing `db.Connection`. Past versions are accessible read-only.
 * The set of valid substores is defined at initialization and cannot be updated dynamically in an existing store instance.
 
 ### `CommitMultiStore`