chore: update TM dep + go.mod cleanup (backport #175)

[mergify]

This is an automatic backport of pull request #175 done by Mergify.
Cherry-pick of 772e828 has failed:

On branch mergify/bp/v0.45.0x-osmo-v8/pr-175
Your branch is up to date with 'origin/v0.45.0x-osmo-v8'.

You are currently cherry-picking commit 772e82855.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   server/tm_cmds.go
	modified:   server/util.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[alexanderbez]

Replaces #195. The original PR should've been backported to the 0.45.x-v8 branch, I just didn't know that existed.

@ValarDragon can you do a quick sanity check on the updated deps in go.mod please? The only one I'm unsure about is the replaced IAVL one (v5 -> v7).

[alexanderbez]

@p0mvn does the data race reported by one of the CI runs mean anything to you?

https://github.com/osmosis-labs/cosmos-sdk/runs/6038036518?check_suite_focus=true

[ValarDragon]

looks good to me as well!

[ValarDragon]

The go race failures are unrelated, we need to get this commit into the v8 branch to fix it: #158