After the superchain-registry is updated such that all chain configs include a depset, op-program will need to read and use the appropriate depset(s) from the chain configs.

From @ajsutton:
"We want to avoid parsing the depset multiple times as it increases runtime a fair bit. So just loading the depset for one chain and depending on it being consistent for all chains makes sense (especially since we will have tests in superchain-registry to ensure the configs are consistent).

Given the loading code is generally shared I suspect op-supervisor would just do the same and load a single depset config."