all: reduce the chain db size

[gzliudan]

Proposed changes

This PR fixes the issue #570. It reduces the size of chain database by the following PRs from geth:

• core: remove unnecessary fields in log ethereum/go-ethereum#17106
• types, rawdb, core, miner: add block location fields to receipt ethereum/go-ethereum#17662
• core/types: fix receipt legacy decoding ethereum/go-ethereum#19182
• core, eth, les, light: avoid storing computable receipt metadata  ethereum/go-ethereum#19345
• core: lookup txs by block number instead of block hash ethereum/go-ethereum#19431

Changelog:

• database version 4
  • the BlockNumber, TxHash, TxIndex, BlockHash and Index fields of log are deleted
  • the Bloom field of receipt is deleted
  • the BlockIndex and TxIndex fields of txlookup are deleted
• database version 5
  • the TxHash, GasCost, and ContractAddress fields are no longer stored for a receipt
  • the TxHash, GasCost, and ContractAddress fields are computed by looking up the receipts' corresponding block
• database version 6
  • Transaction lookup information stores the corresponding block number instead of block hash

Notice: this PR only make new data smaller, we will reduce the old data in another PR later.

Types of changes

What types of changes does your code introduce to XDC network?
Put an ✅ in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)
• Regular KTLO or any of the maintaince work. e.g code style
• CICD Improvement

Impacted Components

Which part of the codebase this PR will touch base on,

Put an ✅ in the boxes that apply

• Consensus
• Account
• Network
• Geth
• Smart Contract
• External components
• Not sure (Please specify below)

Checklist

Put an ✅ in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

• This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
• Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
• Tested the backwards compatibility.
• Tested with XDC nodes running this version co-exist with those running the previous version.
• Relevant documentation has been updated as part of this PR
• N/A