feat(protocol): introduce ForkManager to improve protocol fork management

[dantaik]

Currently, the TaikoL1 protocol required each fork's codebase to contain implementations for both the current fork and the next fork within the same contract. This created unnecessary code complexity and tight coupling between fork versions.

With the new ForkManager, we can:

• Split fork implementations into separate, focused contracts
• Maintain cleaner separation of concerns between fork versions
• Support multiple forks as long as their storage layouts remain compatible

This change improves code maintainability and makes the fork upgrade process more modular.

BTW, I'm aware of Diamond proxy design but I'm in favor of this ForkManager implementation for its simplicity.

[dantaik]

The storage layout of ForkManager is compatible with the layout of TaikoL1.

[openzeppelin-code]

feat(protocol): introduce ForkManager to improve protocol fork management

Generated at commit: b01e6c3abe604c6c873fe7c7b4d3ea17f167a316

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	3 3 0 7 42 55
Dependencies	Critical High Medium Low Note Total	0 0 0 0 0 0

---

For more details view the full report in OpenZeppelin Code Inspector