ethclient: fix invalid params in eth_call, made ethclient support other EVMs network

[hector-nguyen-vmo]

I was using ethclient to query contract in other EVMs, but mostly only support data field instead input, while ethereum support both.

Replacement input with data for eth_call in ethclient:

{
    "jsonrpc": "2.0",
    "method": "eth_call",
    "params": [
        {
            "to": "0xdAC17F958D2ee523a2206206994597C13D831xxx",
            "input": "0x06fddxxx"
        },
        "latest"
    ],
    "id": 1
}

to

{
    "jsonrpc": "2.0",
    "method": "eth_call",
    "params": [
        {
            "to": "0xdAC17F958D2ee523a2206206994597C13D831xxx",
            "data": "0x06fddxxx"
        },
        "latest"
    ],
    "id": 1
}

[holiman]

Previous:
This PR wanted to revert back to data: #28204
Here's where we switched to use input: #28078

I'll lift this from the older PR:

Please ping the relevant projects that they are not in sync with the spec (6 years out of sync). The simplest thing to do is on server side to accept both, and gradually transition clients to input from data. We kind of allowed 6 years transition period in Geth.