chore: adapt push-chain-node to cosmos/evm v0.6.0

[0xNilesh]

Node-side half of the cosmos/evm v0.6.0 upgrade for the audit-fixes line. Pairs with pushchain/push-chain-evm#47.

Important

Merge order. push-chain-evm#47 must merge first, and the pin here must then be re-pointed at the resulting audit-fixes commit. Right now go.mod points at 9031914c on the PR branch chore/evm-0.6.0-on-audit-fixes, which is not a merged commit. Do not merge this before that is corrected.

Why

audit-fixes (and so main/mainnet) sits on the evm v0.5.1 line while develop and testnet/donut have run v0.6.0 since 2026-06-27. That gap is what F-2026-18785 reports; evm#47 closes it. This PR is what makes the node compile and pass against it.

What changed

v0.6.0 makes two breaking changes that reach the node:

1. cosmos/evm removed its custom x/ibc/transfer wrapper. Imports move to standard ibc-go, the keeper no longer takes an Erc20Keeper, and the ERC-20↔IBC conversion that wrapper used to do is now performed by the erc20 IBC middleware wrapped around the transfer stack:

transferStack = erc20.NewIBCMiddleware(app.Erc20Keeper, transferStack)

2. CallEVM gained stateDB and callFromPrecompile parameters — touching x/uexecutor/keeper/evm.go, gas_fee.go, expected_keepers.go, the generated EVM-keeper mock, and every call site in tests.

How it was produced

Cherry-picked 46c77ca4 ("feat: evm 0.6.0 adjustment changes") from #272, which did this same adaptation on develop. It applied with no conflicts. Three deviations, all deliberate:

• Skipped 06c83206 and ff085772 — feat: evm 0.6.0 adjustment changes #272 added an evm-v0.6.0 upgrade handler and then reverted it in the same PR, because the handler belongs on testnet/donut (that landed separately as chore: evm v0.6.0 upgrade handler (donut) #282). audit-fixes is a fresh-genesis branch, so no handler here. Same reasoning as fix: F-2026-18197 | [Dual Defense] Nested Message Dispatch Bypasses EVM Ante for MsgEthereumTx #317 dropping its remove-group handler.
• Retargeted the pin. 46c77ca4 left github.com/cosmos/evm => ../evm, a local filesystem replace that feat: evm 0.6.0 adjustment changes #272's later commit 97f779ae cleaned up. Replaced with the real pseudo-version for evm#47's merge commit.
• Fixed one call site feat: evm 0.6.0 adjustment changes #272 could not have known about. test/integration/uexecutor/inbound_multicall_outbound_atomicity_test.go:460 was added to audit-fixes after feat: evm 0.6.0 adjustment changes #272 was authored and still used the old CallEVM signature. Adapted to match the form its sibling files already use.

Tests

Full suite against the v0.6.0 pin, run serially to avoid local disk contention:

go test -mod=readonly -p 1 -tags="ledger test_ledger_mock test" ./test/integration/...
  exit=0  ok=6   FAIL=0   disk errors: 0

go test -mod=readonly -p 1 -tags="ledger test_ledger_mock test" ./app/... ./x/... ./utils/...
  exit=0  ok=15  FAIL=0   disk errors: 0

21 packages green, no failures. go build ./... and go mod tidy clean.

The integration run is the meaningful one — test/integration/uexecutor is where the CallEVM signature change actually bites, and it is where the one real breakage surfaced and was fixed.

Scope

This is a version bump plus the mechanical adaptation. No behavioural change is intended on the node side, and no upgrade handler is included. The single audit finding closed by the upgrade (F-2026-18785) is fixed in the evm repo, not here — see evm#47 for that analysis and for which evm-attributed findings the upgrade does not address.