api: remove computationcost limit at call/estimate apis

[yoomee1313]

Proposed changes

• Lift computation cost limit at klay_call, klay_estimateGas, klay_estimateComputationCost, eth_call, eth_estimateGas.

• No need to use experimental computation cost flag (--opcode-computation-cost-limit) as an attempt to bypass the cost limit. The limit is always infinite in such APIs.

• Computation cost limit after this PR:

  • block syncing & other APIs: Use hard-coded limit (params.OpcodeComputationCostLimit).
  • block syncing & other APIs, with --opcode-computation-cost-limit: Use the specified number
  • call/estimate APIs: always infinite

> eth.estimateGas({"to":"0xE46888D56CfE7804d045aDcdaFEc548E0329c965", "data": "0x53ae5a540000000000000000000000000000000000000000000000000000000000013e00"})
27873306
> klay.estimateComputationCost({"to":"0xE46888D56CfE7804d045aDcdaFEc548E0329c965", "data": "0x53ae5a540000000000000000000000000000000000000000000000000000000000013e00"})
"0x37574e27"

Types of changes

Please put an x in the boxes related to your change.

• Bugfix
• New feature or enhancement
• Others

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING GUIDELINES doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes ($ make test)
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Related issues

• Result of klay_estimateComputationCost #2081
• Frequently returned reached the opcode computation cost limit #2083

Further comments

• Reimpose the evmtimeout on the estimateGas api and it was �once erased in Add revert error reason at klay_call, klay_estimateGas #1408.