feat(taiko-client): changes based on Pacaya fork

[davidtaikocha]

TODO:

• add more tests for Pacaya changes
• test legacy Ontake code
• fix current tests, need @YoGhurt111 to add OP verifier at first
• improve current code
• add preconf block API server
• add preconf blocks P2P network
• do not reorg the current chain when there is a BatchProposed event

[openzeppelin-code]

feat(taiko-client): changes based on Pacaya fork

Generated at commit: 88a78c5955ce1ce65fc685d7a1971ecc0267f855

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	3 3 0 10 40 56
Dependencies	Critical High Medium Low Note Total	0 0 0 0 0 0

---

For more details view the full report in OpenZeppelin Code Inspector

[davidtaikocha]

@davidtaikocha we need to check if the resolver has a preconf_router set, and if so, we need to use the generated PreconfROuter to propose blocks through - otherwise, we use the TaikoInbox.

changed: 9c9e47a

[mask-pp]

Suggested change

	L1BlockHeight: meta.GetRawBlockHeight(),
	L1BlockHash: meta.GetRawBlockHash(),
	L1BlockHeight: nil,
	L1BlockHash: common.Hash{},

[mask-pp]

Due to this IsPreconfBlock check in taiko-geth.