chore: upgrade cosmos/evm v0.6.0 → v0.6.2 on develop

[0xNilesh]

Brings develop from cosmos/evm v0.6.0 to v0.6.2 (13 upstream commits).

No migration required

• no .proto changes
• no migration or upgrade files
• no ConsensusVersion bumps
• no store-key or Params changes

This is a code-only upgrade. On the node side it is a replace pin bump (not in this PR).

Merge

One conflict, contracts/solidity/ContractCreationTester.sol — purely line-wrapping of the same
statement; kept the branch's formatting. Everything else auto-merged.

⚠️ Module accounts may no longer receive EVM balance

The v0.6.1 security merge (3524ebc6, private fork merge) adds to SetBalanceWithLocked:

if acct := k.accountKeeper.GetAccount(ctx, cosmosAddr); acct != nil {
    if _, isModule := acct.(sdk.ModuleAccountI); isModule {
        return errorsmod.Wrapf(errortypes.ErrUnauthorized, "%s is not allowed to receive funds", cosmosAddr)
    }
}

The guard runs before the delta computation, so it errors even when the balance is unchanged, and
statedb.Commit calls SetAccount (→ SetAccountBalance → SetBalanceWithLocked) for every dirty
account. Upstream moved their own test helpers off module-account deployers for this reason
(changelog cosmos#1243: "the EVM commit path may not write a module account's balance").

This does not surface in this repo's tests (0 guard hits), but push-chain-node makes EVM calls FROM the
ue-module account (isModuleSender=true, 4 sites in x/uexecutor/keeper/evm.go). Those paths must be
exercised before the node pin is bumped. Node-side work is deliberately out of scope here.

Tests

• go build ./... clean
• ./x/vm/... ./x/erc20/... ./x/feemarket/... ./precompiles/... — 15 packages ok, 0 fail
• evmd/tests/integration — the only failures are pre-existing on develop: verified by running the
  same suite on unmodified origin/develop and diffing the failing assertions, which are identical
  (TestPreciseBank*, reserve expecting 2 integer coins, getting 1). Zero not allowed to receive funds
  errors in either run.