Output L1 fields in API v2 for transaction and fix transaction fee calculation

[varasev]

This PR adds the following fields to transaction in API v2:

• L1 fee
• L1 fee scalar
• L1 gas price
• L1 gas used by Txn

These fields are contained in eth_getTransactionReceipt response. If some field doesn't exist, it won't be included into API v2 response.

Also, this PR adds L1 fee to the fee so that fee equals to l2_execution_fee + l1_data_fee as described in https://community.optimism.io/docs/developers/build/transaction-fees/. For L1 chains L1 fee will be zero and the fee will be calculated as usual, so this change is backward compatible.

Checklist for your Pull Request (PR)

• I added an entry to CHANGELOG.md with this PR
• If I added new functionality, I added tests covering it.
• If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
• I checked whether I should update the docs and did so by submitting a PR to https://github.com/blockscout/docs
• If I added/changed/removed ENV var, I submitted a PR to https://github.com/blockscout/docs to update the list of env vars at https://github.com/blockscout/docs/blob/master/for-developers/information-and-settings/env-variables.md and I updated the version to master in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.
• If I add new indices into DB, I checked, that they are not redundant with PGHero or other tools