feat(pool): add da tracking to pool

[dancoombs]

Closes #744

Proposed Changes

• Add da_gas_tracking_enabled CLI parameter.
• Cache any returned DA UO data with each UO in the pool upon entry
• If tracking is enabled, on each block, pull the block data, then sync calculate the required pvg of each UO to set eligibility
• Only return eligible UOs to the builder when queried
• Repeat the sync calc in the builder (can this be removed?)

TODO

• Determine if we can remove the builder PVG check Decided the builder must keep this, as it may raise the fees compared to the initial fees used by the mempool.
• Performance check on the do_maintenance call on the pool when under heavy load
• Doc updates
• More tests [provider] Add more unit test for cached DA oracles #845

[dancoombs]

Tests to be added in this ticket #845

[dancoombs]

Filled a mempool on my laptop on op-sepolia with 1000 UOs, the pool maintenance call took < 5ms.

I'd expect it to be closer to 1-2ms on good/isolated hardware. So I don't think we have a performance problem with the pool maintenance loops. Not going to do anything there for now. If we eventually see issues we have 2 levers to pull: (1) optimize the code (2) move to rayon blocking pool.

[dancoombs]

Also closes #859

[0xfourzerofour]

Looks good just a couple comments