op-node: read BlockTime, SeqWindowSize from superchain-registry configs

[bitwiseguy]

Description

• Update the version of go superchain-registry/superchain module import
• Update op-node to read BlockTime and SequencerWindowSize from superchain.ChainConfig during LoadOPStackRollupConfig

Additional Context

Fixes ethereum-optimism/superchain-registry#390

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.69%. Comparing base (c55ade0) to head (4ff66bb).
Report is 3 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff              @@
##           develop   #11172       +/-   ##
============================================
+ Coverage    60.69%   79.69%   +18.99%     
============================================
  Files           20       12        -8     
  Lines         1781     1246      -535     
  Branches        71        0       -71     
============================================
- Hits          1081      993       -88     
+ Misses         667      220      -447     
  Partials        33       33               

Flag	Coverage Δ
cannon-go-tests	79.69% <ø> (ø)
chain-mon-tests	?
sdk-tests	?

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

see 8 files with indirect coverage changes

[geoknee]

Once this is merged, we can go back and update the validation module in the superchain-registry to pull in these changes.

[protolambda]

Change LGTM. We have some tests already that check a few frozen configs against what the registry generates, and those still pass, so the values are correctly set.