Supplement baseFee and gasLimit for pre gingerbread blocks

[Kourin1996]

Closes https://github.com/celo-org/celo-blockchain-planning/issues/384

This PR adds baseFeePerGas and gasLimit to the response of pre Gingerbread block in JSON-RPC

[piersy]

Hi @Kourin1996, looks good overall, but I don't see a reason to store the gas limit in the database, when we have it hardcoded. So I would just store the base fee.

Also how did you get your benchmark results? https://github.com/celo-org/celo-blockchain-planning/issues/384#issuecomment-2553929355

[Kourin1996]

@piersy

Also how did you get your benchmark results? https://github.com/celo-org/celo-blockchain-planning/issues/384#issuecomment-2553929355

Set up a local cluster using simple-celo-node, but create a new Dockerfile under op-geth.
After run scripts to send JSON-RPC requests of eth_getBlockByNumber over a million blocks. Record the average response time using two types of codebases: (1) Retrieving gasPrice with each request and (2) Loading data from local database first, and retrieving gasPrice from the receipt only if the record does not exist

[palango]

Question regarding the general approach: we could also do those calculations during the migration right. That would trade some complexity there for simpler code in the codebase. Any opinions on that?

[piersy]

Question regarding the general approach: we could also do those calculations during the migration right. That would trade some complexity there for simpler code in the codebase. Any opinions on that?

The problem with that approach is that we are not syncing this data, so if we did that, snap sync nodes would not have it. So I think it's better to calculate it on demand as it is done here.

[piersy]

Looking good @Kourin1996!