chore(deps): bump github.com/ethereum/go-ethereum from 1.10.13 to 1.12.1

[dependabot[bot]]

Bumps github.com/ethereum/go-ethereum from 1.10.13 to 1.12.1.

Release notes

Sourced from github.com/ethereum/go-ethereum's releases.

Antibaar (v1.12.1)

Geth v1.12.1 is a maintenance release, albeit a rather large one, since we haven't put out a version since May. This release is a recommended upgrade for all users and contains security-related fixes.

Here's the list of changes:

Cancun fork

Development for the upcoming Cancun hard fork has been a focus in this release cycle. Do note however, that Geth v1.12.1 is not yet ready for Cancun.

• For EIP-4844 'Shard Blob Transactions', this release contains basic type definitions and state transition logic (#27356, #27382, #27392, #27393, #27470, #27721, #27736, #27743, #27767, #27789, #27791, #27793, #27796, #27797, #27825, #27874)
• We have also implemented an entirely new mempool -- the blobpool -- for EIP-4844 transactions. The new pool is backed by an on-disk database and has an overall simpler design than the txpool we use for regular transactions. The blobpool is not yet used by p2p networking and is still being tested in the Cancun devnets. (#26940, #27429, #27463, #27481, #27790, #27822)
• EIP-6780: 'SELFDESTRUCT only in same transaction' (#27189)
• EIP-5656: 'MCOPY instruction' (#26181)
• EIP-1153: 'Transient storage opcodes' was already implemented and is enabled for Cancun (#27663, #27613)

Geth command changes

• The Rinkeby testnet is no longer supported in Geth (#27406)
• geth --dev now simulates a PoS-based chain (#27327)
• evm blocktest can now output structured logs (#27396)
• Geth will now configure GOMAXPROCS based on CPU quota settings. This should improve efficiency when running in Docker containers with a CPU core limit applied. (#27506, #27814)
• An IPv6 listening address for can now be configured for HTTP/WS (#27628) (#27635)

RPC/GraphQL API changes

• JSON transactions now have a yParity fields, as mandated by the RPC API spec (#27744, #27882)
• Legacy transactions now have a chainID field in RPC responses, like all other transaction types (#27452)
• Block headers returned by RPC no longer report a non-standard size field (#27347)
• eth_estimateGas now supports state overrides like eth_call (#27845)
• eth_estimateGas now handles internal chain reorgs more correctly (#27505)
• eth_getProof is slight more efficient, and will now return a response in the canonical encoding even for off-spec input parameters (#27309, #27310)
• eth_getTransactionReceipt now returns null when the transaction is not available. It used return an error in that case. (#27712)
• debug_storageRangeAt now takes a block hash or number as parameter (#27328)
• The new debug_getTrieFlushInterval method reports the internal state saving interval (#27303)
• A crash in the prestate tracer is resolved (#27691)
• Structured EVM logs returned by tracing now contain the returnData (#27704)
• GraphQL now supports withdrawals (EIP-4895) (#27072)

Go library changes

• The RPC server now enforces limits on batch requests and responses. This is a potentially breaking change. If you use batch requests with geth, and also use the go-ethereum RPC client library, we strongly recommend updating your go-ethereum library dependency as well. The new client version handles invalid batch responses way better than before. (#26681)
• The RPC client has multiple new ways to test whether the transport supports real time subscriptions (#25942)
• fsync is now enabled for pebble database writes (#27615, #27522)
• Function calls timed by metrics will now run even if metrics are disabled (#27724, #27723)
• Node.Attach no longer returns an error. This is a breaking Go API change. (#27450)
• The keystore has improved verification of keys loaded from disk (#27432)
• Per-level metrics are now available for LevelDB (#27643)

... (truncated)

Commits

• 9c216bd params: release go-ethereum v1.12.1
• 6797902 core/state: move UpdateContractCode before the trie hash is computed (#27853)
• 10d9f93 graphql: add yParity field for transactions (#27882)
• 7ec60d5 p2p: move ping handling into pingLoop goroutine (#27887)
• e13fa32 core/vm: update 4844 - point evaluation precompile address (#27874)
• 0d772b9 graphql: avoid greedy allocation (#27873)
• 6d2bcb9 p2p/simulations/examples: use atomic.Int64 (#27861)
• eeebb07 internal/ethapi: add state override to estimateGas (#27845)
• d14c07d accounts: use atomic type (#27857)
• 8574767 internal: use atomic type (#27858)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/Consensys/quorum-key-manager/network/alerts).

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}