op-node: Only deploy CrossL2Inbox if there is more than one chain in the dependency set

[ajsutton]

Description

Makes the deployment of CrossL2Inbox predeploy conditional on their being more than one chain in the dependency set. As there isn't currently support for adding chains to the dependency set, the condition is currently only checked at the interop activation block - when adding chains is supported this will have to be expanded to check at the block the dependency set actually changes. That's not implemented now because there isn't even a mechanism to specify the timestamp that a dependency set change activates at yet.

Most of the changes are plumbing to pass the dependency set through to the attributes builder so it can determine which upgrade transactions are required.

Metadata

#16041

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.24%. Comparing base (6bf2ef5) to head (5cdec51).
Report is 13 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff              @@
##           develop   #16042       +/-   ##
============================================
+ Coverage    82.34%   96.24%   +13.89%     
============================================
  Files          161      106       -55     
  Lines         8812     4575     -4237     
============================================
- Hits          7256     4403     -2853     
+ Misses        1416      172     -1244     
+ Partials       140        0      -140     

Flag	Coverage Δ
cannon-go-tests-64	?
contracts-bedrock-tests	96.24% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 55 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[tynes]

Clarifying that based on ethereum-optimism/specs#707, the L2ToL2CrossDomainMessenger will always be deployed and the CrossL2Inbox will be deployed if the depset > 1

[ajsutton]

Clarifying that based on ethereum-optimism/specs#707, the L2ToL2CrossDomainMessenger will always be deployed and the CrossL2Inbox will be deployed if the depset > 1

Yes the implementation does this, just the description and title was written way back before the details were known.