Design for KZG commitment

[qizhou]

After BLOBs with KZG commitment are supported by EIP-4844/Danksharding, we need to investigate early how to support KZG commitment in our storage contract. A couple of early thoughts:

• The KZG commitment is a 31-byte versioned hash, while we truncate the current commitment to 24 bytes. The truncated version works for Merkle tree root for proof verification (mine()) or value verification (verify()). Verifying data KZG commitment needs support from new precompiles that are available in EIP-4844. However, I am not sure whether the new precompiles can still work with truncated commitments.