[DO NOT MERGE] PoC for E2E testing with Kurtosis

[syjn99]

What type of PR is this?

Other

What does this PR do? Why is it needed?

Explore the feasibility for migrating the current E2E code to Kurtosis (ethereum-package) + Assertoor.

Which issues(s) does this PR fix?

PoC for #15320

Other notes for review

• Nov. 30: Build local docker images and spin up a new devnet with them. Dora is temporaily added for checking the devnet.
• Current status (Dec. 3): Run with minimal config. Launch Assertoor with basic transaction test.

Acknowledgements

• I have read CONTRIBUTING.md.
• I have included a uniquely named changelog fragment file.
• I have added a description to this PR with sufficient context for reviewers to understand this PR.

[syjn99]

I might add new oci_tarball with different name to build images only for E2E test.

[satushh]

What would be the next steps?

[syjn99]

What would be the next steps?

Currently, this branch provides an easy way to spin up a new devnet for E2E with customized configurations. Next steps are simple: exploring assertions (or evaluators for the current E2E testing codes). At this moment, I have a couple of things on my head:

1. Use assertoor: We don't have to maintain the testing package in our own, just use the existing tool that is nicely maintained by ethPandaOps. Simple YAML files for each assertion will be the declarative way to add/delete new assertions for E2E. However, not all evaluators can be matched with existing tasks in assertoor - which means we need to write own shell scripts for those assertions. Also, from my understandings, assertoor doesn't support "assertion on every epoch" - it only supports cron-based instruction.
2. Use existing evaluators: As it is easy to interact with a specific service in Kurtosis enclave, we might replace gRPC calls into REST API calls and then reuse those evaluators.

[syjn99]

@prestonvanloon @satushh
Related write-up: https://hackmd.io/@junsong/ry8SnMFbWg