op-challenger: Migrate config over to supporting multiple L2s #13833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updates the op-challenger config and flags to support multiple L2 endpoints and network/configs.
It currently enforces that if single chain game types are active, then only one L2 config/endpoint can be specified. I don't think we'll need to support running a challenger that works for both single chain and interop chain games in the same DisputeGameFactory but if we do we can work out how to rationalise things then.
Tests
Updated unit tests.
Additional context
Builds on #13810