feat: adding permit2 support to SuperWETH and SuperchainERC20

[0xng]

Description

Adds Permit2 support to SuperchainWETH and SuperchainERC20 contracts.

Information and Questions

Solady doesn't make use of its allowance function in transferFrom, instead it computes and reads from the slot directly. This means that overriding the allowance function doesn't affect the transferFrom function. For this reason I had to override transferFrom and add a special case for when PERMIT2 is the msg.sender. The logic within that if block is the same transferFrom performs when updating the balances of from and to.

Despite allowance not being used in transferFrom I still overrode it in case integrators fetch it to perform further logic. If I hadn't it would return 0 and that may mess up some of their logic.

When it came to SuperchainWETH I noticed it inherited from WETH98 which has allowance as a public mapping. This means it can't be overriden. I came up with two potential approaches:

1. Following OZ's pattern of renaming allowance to _allowances and making it a private state variable. This allowed me to add an allowance getter and to make it virtual so I could override it easily. This also meant modifying a bit of logic from this contract and from DelayedWETH.
2. Making transferFrom virtual and adding the case when PERMIT2 is the caller at the beginning.

I went for approach 2. However this approach doesn't reflect the virtual allowance of PERMIT2, so I'm not 100% sold this is the best approach. The main reason why I chose it was because it didn't affect the logic (other than adding a virtual keyword) of WETH98 nor any contract that inherited from it, and because I was not certain whether there were certain design guidelines that WETH98 had to follow.

I can implement the first approach quickly if needed. Also any other potential approached that I may have missed are welcomed.

One more doubt I had was whether to add this logic to the SuperchainERC20 or not. By adding it here we are forcing all contracts extending from it to support Permit2. Extension can then opt-out. Another approach would be to not add it to the SuperchainERC20 and have the extensions opt-in instead.

Lastly, these implementations and the current one on OptimismMintableERC20 doesn't have a way to revoke the infinite allowance. Are we sure we don't want to add this?