feat(provider): add cached DA oracles for bedrock/nitro

[dancoombs]

Proposed Changes

• Bedrock DA oracle with caching
  • Add a local DA provider for optimism bedrock chains. This requires a single network call per block to calculate the required DA gas for every user operation.
  • The DA provider contains an LRU cache to ensure that we only issue 1 network call update per block.
  • Compression happens locally now, via a fastlz binding at a specific commit. This commit is specifically the same used by LibZip.sol, which is used by the optimism DA oracle contract.
• Nitro DA oracle with caching
  • The oracle only makes 1 network call per new UO + 1 network call per block
  • Due to the nitro implementation, there is the possibility of rounding errors, which are reduced here by scaling. Errors should underestimate by a small margin

[dancoombs]

Will add more tests in this ticket: #845

Want to get the mempool usage PR up quickly.

[andysim3d]

question: I get the idea of this method and above are for impl the trait. could we move those impl in the trait definition so they by default return empty?

[dancoombs]

I typically don't like default method implementations, especially when they can cause panics, typically means the interface is wrong.

I think the better way to fix this would be to move the 3 new methods into a new trait: DAGasOracleSync so that we can be sure they only get called if they're implemented.

Then instead of using the da_tracking_enabled bool we pass an Option<DAGasOracleSync> to the pool/builder which uses it if populated.

For the sake of time I'm going to add a ticket to clean this up. Might move it to v0.5

[dancoombs]

#850