op-node: parallel events executor

[protolambda]

Description

This adds a new event executor: parallel deriver execution.
Events are queued up, with a customizable capacity per deriver.
A parallel go routine per deriver then dequeues events, and processes them.

Each deriver has its own thread, creating parallelism, but with local state per deriver we simplify a lot of interactions still; no need for locking per individual variable.

This depends on #11099

TODO:

• Parallel executor unit testing
• Make it the default for all op-e2e tests to use the parallel executor (except for action testing)
• Add hidden/beta CLI config flag to op-node to switch to this executor
• Review race conditions / locks of derivers, to make sure parallel deriver execution is safe

Experimental

Tests

Work in progress.

Metadata

Fix #10864

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[protolambda]

Still hoping to pick this work back up once other interop related work cools down

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[maurelian]

@protolambda I see that you added the exempt stale label to this. But it's now extremely stale, can it be closed?

Actually I see that you referenced this PR from #13752 as something you still want to get in.