fix(rpc): Add l1 block info to OpTransactionReceipt

[emhane]

Motivation

Closes #54

Solution

• Moves L1 block info fields out of type OptimismTransactionReceiptFields into new type L1BlockInfo.
• Adds L1BlockInfo to OpTransactionReceipt

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[refcell]

This makes sense - would like to see a PR down the road that adds doc comments about why these are separate types and how they're used. If you're looking at op-geth, these fields are just part of the receipt and not also a separate OptimismTransactionReceiptFields.

[emhane]

This makes sense - would like to see a PR down the road that adds doc comments about why these are separate types and how they're used. If you're looking at op-geth, these fields are just part of the receipt and not also a separate OptimismTransactionReceiptFields.

the deposit envelope has the deposit nonce and receipt version fields. so adding the OptimismTransactionReceiptFeilds type to OpTransactionReceipt directly would have caused duplicates for these keys.

I think down the road, this will be replaced with some new envelope types, as #53, to help set the additional op fields. right now it's really quite hard to debug anything related to this since I have to memorise which fields have to be set for which fork, from reading docs on the OptimismTransactionReceiptFeilds (now L1BlockInfo) type.

the type OptimismTransactionReceiptFields will probably be depreciated when we can stop using the AnyTransactionReceipt type in reth paradigmxyz/reth#10632, which is possible after next op-alloy release to include this pr. when the linked issue is solved, we can just call a builder for OpTransactionReceipt directly, no need for intermediary type OptimismTransactionReceiptFields to convert to OtherFields.