[Feature]: make transaction execution thread-safe

[yihuang]

Summary

When experimenting with parallel transaction execution, I noticed several race conditions in current transaction execution flow.

Problem Definition

there are a few race conditions when trying to execute transactions in parallel.

Proposed Feature

• optional block gas meter
  feat(baseapp): add option to disable block gas meter #19626
• reset the tx context's gas meter at the very beginning in getContextForTx, to avoid accessing a wrong gas meter instance before it's initialized in ante hander.
  fix(baseapp): don't share global gas meter in tx execution #19616

[tac0turtle]

This is accounted for in server v2 design. It might make sense to wait for that and implement a custom stf

[yihuang]

This is accounted for in server v2 design. It might make sense to wait for that and implement a custom stf

I can submit a few trivial cleanups first. it seems it's mostly thread-safe already, in the sense of go test -race not complaining.

[tac0turtle]

closing this as we merged the prs that were proposed