fix: patch the consistency of transaction receipts with a different chain-id

[jasonsong0]

Description

There was a specific block height that used the Evmos default chain ID (9000).
This occurred from v8 to v8.1.1 (block heights from 10848200 to 10849447).

Due to this issue, third-party services encountered an 'invalid chain-id' error when attempting to verify transaction results.
This patch addresses the problem by ensuring that the transaction receipt returns the same results as before.

Check this PR for details

ps.
There was an issue with the PR process, so the commits already included in v8.1.2 were also included.
You can ignore the first three commits(904f07a, d1b7b45, 84537d7)

---

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...

• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• included the necessary unit and integration tests
• reviewed "Files changed" and left comments if necessary

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 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)

[dudong2]

LGTM