refactor: avoid using NoopTransactionPool in OP payload builder

[klkvr]

Right now OP payload builder depends on NoopTransactionPool tx type when building empty payloads or constructing witnesses. This is unconvinient because we don't know the PoolTransaction AT there

This PR changes logic to operate on a simple closure BestTransactionsAttributes -> iterator which may optionally capture and use the pool. That way for building a payload without external transactions we no longer need to mock the pool

Likely a nicer solution could be to force payload builders to hold a pool, this would also allow simplifying the BuildArguments struct although has other implications as this would leak pool generic to some rpc types which deal directly with payload builder

[codspeed-hq]

CodSpeed Performance Report

Merging #13547 will improve performances by 15.59%

_{Comparing klkvr/refactor-op-builder (f228404) with main (41283d3)}

Summary

⚡ 1 improvements
✅ 76 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	klkvr/refactor-op-builder	Change
⚡	`hash builder[init size 1000	update size 100	num updates 1]`	2.7 ms

[mattsse]

yep, this is better