op-test-sequencer: initial service scaffolding

[protolambda]

Description

Completes milestone 0.0 of the test-sequencing work.

Code is largely inspired by the op-supervisor service setup code.
Previous work to de-duplicate more service code was blocked, so we have to go with some boilerplate here.

Tests

Tests CLI usage, service entrypoint RPC, mock backend.

Additional context

Metadata

Fix #14123

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.01%. Comparing base (0a2f43d) to head (48e58e6).
Report is 49 commits behind head on develop.

❗ There is a different number of reports uploaded between BASE (0a2f43d) and HEAD (48e58e6). Click for more details.

HEAD has 5 uploads less than BASE

Flag	BASE (0a2f43d)	HEAD (48e58e6)
cannon-go-tests-32	2	0
cannon-go-tests-64	2	0
contracts-bedrock-tests	1	0

Additional details and impacted files

@@             Coverage Diff              @@
##           develop   #14270       +/-   ##
============================================
- Coverage    78.11%   42.01%   -36.11%     
============================================
  Files          178      859      +681     
  Lines        10667    78436    +67769     
============================================
+ Hits          8333    32957    +24624     
- Misses        2143    42586    +40443     
- Partials       191     2893     +2702     

Flag	Coverage Δ
cannon-go-tests-32	?
cannon-go-tests-64	?
contracts-bedrock-tests	?

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

see 1029 files with indirect coverage changes

[axelKingsley]

This scaffolding does indeed look a lot like the supervisor, without any business logic.

I'm inclined to suggest that we somehow turn this commit into a template that can be used in the future. Rather than have this PR use op-test-sequencer/, it could use op-service-template/. We could then spawn the op-test-sequencer by cloning the directory, and filling out any missing names.

Or, at a minimum, this commit should be mentioned in some README.md so future apps may reuse this scaffolding.

[protolambda]

Tracking the service-templating suggestion here now: #14577
There is no readme where we can put this PR link / commit well, but the issue should help surface this for future use if needed.