Cherry-pick of db6b608 has failed:

On branch mergify/bp/v0.38.x/pr-3031
Your branch is up to date with 'origin/v0.38.x'.

You are currently cherry-picking commit db6b60822.
  (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:
	new file:   .changelog/unreleased/bug-fixes/3002-invalid-txs-results.md
	modified:   rpc/core/blocks.go
	modified:   rpc/core/blocks_test.go
	new file:   state/compatibility_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   state/errors.go
	both modified:   state/state_test.go
	both modified:   state/store.go
	both modified:   state/store_test.go

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

there are many conflicts in this backport, will manually take care of it

Comments for the reviewers of this backport. I had to manually go through and implement some of the backport changes to adapt them to v0.38.x.

There are some changes from the original PR that needed some "adaptation"

• There is an error log message that I've added to the BlockResults in the rpc/core/blocks.go as opposed to the one in state/store because the Logger is not available in there. We'd need to include a logger in the StoreOptions that is part of the dbStore so this would need a lot of changes that could even be breaking. Logging the message in rpc is fine because the method from store is only called from there.

• The compatibility_test tests from the original PR are not really usable in v0.38.x because we don't have the versioned protos in there. Most of the tests in compatibility are related to the versioned protos. But I've kept and adapted some logic so we can at least try to simulate and test the saving of a legacy ABCI response to the store and the loading as a ResponseFinalizeBlock.