chore: prepare v0.46.8 release

[julienrbrt]

Description

Prepare v0.46.8 release.
Add replace to point to Informal System fork of Tendermint (as per twitter.com/informalinc/status/1613580977980473346).

Changes tested against a Quicksilver node (v0.46.8-0.20230107121918-36784a8a7a93).

---

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)

[alexanderbez]

Are all chains that upgrade to v0.47 doing to have to do this as well? If so, we should reference this in the release notes & upgrading guide (if we have not already).

[julienrbrt]

That is a good one, let me add that in the release notes. We should do that for v0.45 too.

[tac0turtle]

do we need this for 0.46 and 0.45? I would think not?

[julienrbrt]

The replace or the mention?

[tac0turtle]

the replace, we can mention it, but its also not required

[alexanderbez]

Any where we have a replace for Tendermint I think a chain would need a replace too because Tendermint dep is used in app-specific stuff like cmd. So updating our docs/guides will be necessary.

[julienrbrt]

I think the advice is to use the replace given that you could rewrite git history (go.sum should detect that but still - for new chains you don't have that guarantee).