refactor(protocol): multiple improvements on implementation and tests

[dantaik]

This is a large PR, with many changes aimed at adapting to recent updates. During your review, please focus primarily on storage and ABI upgradability aspects.

• Introduced IResolver and DefaultResolver

  This update refactors the address resolution process by replacing IAddressManager, IAddressResolver, and AddressManager with a new interface, IResolver, and its implementation, DefaultResolver. Previously, EssentialContract relied on an addressManager contract for address resolution. Now, EssentialContract points to an IResolver instance directly. This update:

  • Removes the need for address caching, enabling a memory-based, pure-function Resolver to reduce gas costs.
  • Supports contract reconfiguration via EssentialContract.setResolver.
  • Eliminates MainnetXXX contracts, which previously handled caching, simplifying the structure.

• Test Cleanup

  The test environment has been streamlined, with common logic refactored and dependencies on real provers minimized. The rollup protocol tests now have three main targets:

  • pnpm test:l1
  • pnpm test:l2
  • pnpm test:shared

  You can also run all tests with pnpm test.

• Removed TierRouter

  Routing logic has been incorporated into the TierProvider implementation, allowing the deletion of TierRouter.

• Deployment Scripts

  Many deployment scripts were designed for one-time use and are not intended for reuse. Redundant scripts were deleted, and others moved to script/layer1/mainnet and script/layer1/hekla. The GitHub workflow has been updated to ignore these scripts.

Todos

• @dantaik script/layer1/DeployProtocolOnL1.s.sol: Working on rewriting this deployment script to improve accessibility for users less familiar with the protocol design. The goal is to make it interactive and/or support input files, with modular scripts for reuse.
• @dantaik Additional test improvements needed before merging this PR.
• @davidtaikochaTests in test/genesis/ were temporarily removed. Please reintroduce them using DefaultResolver (avoid using files from the script/ folder). Submit a separate PR.
• @davidtaikocha Most modified scripts remain untested and may contain issues. Please verify functionality and address issues in separate PRs.
• @smtmfft SP1-related tests are failing; please assist in resolving these. Run with FOUNDRY_PROFILE=layer1 forge test -vvv --mt test_sp1_.
• Additional TODOs are noted in the code; please address them where possible.

[openzeppelin-code]

refactor(protocol): multiple improvements on implementation and tests

Generated at commit: baf6cfa3e904d36a070e8cd06223774fd761fbd8

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	3 3 0 8 42 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

[smtmfft]

@smtmfft SP1-related tests are failing; please assist in resolving these. Run with FOUNDRY_PROFILE=layer1 forge test -vvv --mt test_sp1_.

That is because the tier verifier address changes. I will re-generate proof for the test soon, can ignore these 2 (any maybe risc0 has the same problem) for now as it is not a problem with the code logic.