Add L1 Security gas parameters to transaction receipt

[maxandron]

Related discussion #3775

Premise

On layer 2 optimistic chains, such as Optimism and Base, there is an additional gas fee representing the cost of communicating the transaction to layer 1.

Layer 2 providers return additional fields when calling eth_getTransactionReceipt

Ethers currently doesn't parse these fields, so they are ignored and require implementing the call to eth_getTransactionReceipt manually.

This PR adds support for three variables: l1Fee, l1GasPrice, and l1GasUsed to the getTransactionReceipt.

[dvir1994]

Nice! Including these fields will really help with Layer 2 transactions 👍

[RealJohnnyTime]

Great addition!

[ricmoo]

The properties need to be all marked as ?, since other chains won't have them. There is definitely a need to allow some way to allow more expressive and network-specific properties on transactions and blocks though. I'll look into this and get these properties accessible.

[maxandron]

@ricmoo

There are two options I see to improve usability:

1. Let these properties have a default of 0n if they do not exist (this is what I implemented in my codebase to make it easy to work with multiple chains without considering whether they exist or not)
2. The other option is to convert the type definitions into type instead of interface -> then we can create mutually exclusive properties (all L1 gas properties exist, or all don't exist)
   2.1. Using types instead of interfaces, we can add a boolean that will be false if they do not exist and true if they do

I rather like option one and adding proper documentation to let users know that on chains without L1 fees, these will be set to 0