fix: Update ExtraEIP parameter format for EVM v0.2.0 compatibility

[AryaLanjewar3005]

Summary

Problem

Following the migration from pushchain/evm v0.1.0 to v0.2.0, the format for passing ExtraEIP parameters has changed, causing EVM transaction failures.

Previous format (v0.1.0):

extraEIP = ["ethereum_3855"]

New format (v0.2.0):

extraEIP = [3855]

Impact

The format mismatch caused the EVM interpreter to misinterpret the string "ethereum_3855" as individual ASCII character codes (101, 104, 114, 117, 95, 56, 53), resulting in multiple EIP activation failures:

9:18AM ERR EIP activation failed error="undefined eip 101" eip=101 module=geth
9:18AM ERR EIP activation failed error="undefined eip 104" eip=104 module=geth
9:18AM ERR EIP activation failed error="undefined eip 114" eip=114 module=geth
9:18AM ERR EIP activation failed error="undefined eip 117" eip=117 module=geth
9:18AM ERR EIP activation failed error="undefined eip 95" eip=95 module=geth
9:18AM ERR EIP activation failed error="undefined eip 56" eip=56 module=geth
9:18AM ERR EIP activation failed error="undefined eip 53" eip=53 module=geth

Solution

Updated EVM parameters to use the new integer-based format for EIP specification. Modified the upgrade handler to properly handle this breaking change from the EVM library migration.

References

• Fixes #
• Related issue/PR: V2 upgrade evm#2

Changes

• Updated ExtraEIP parameter format to match v0.2.0 specification
• Modified upgrade handler to accommodate the new EVM parameter structure

Testing

• go test ./...

Checklist

• Ready for review
• Docs updated (if applicable)
• Env vars updated (if applicable)