Kurtosis+E2E: Add doppelganger E2E test

[syjn99]

What type of PR is this?

Other: E2E test

What does this PR do? Why is it needed?

This PR adds a dedicated E2E test (TestEndToEnd_Kurtosis_DoppelgangerProtection) for VC doppelganger detection backed by Kurtosis. In #17045, I decided to separate doppelganger e2e test from normal e2e tests as it has different characteristics:

• Launches new VC process with the keystore from first VC process.
• Checks until a wanted log is printed ("Duplicate instances exists in the network for validator keys").

which adds hacky ways (e.g., run Starlark script to launch new service) to run this test apart from what we normally do with ethereum-package configuration and Assertoor. Thus it would be much better to open a dedicated PR for doppelganger protection and run it in separate way.

In legacy e2e tests, we run testDoppelGangerProtection when a predicate TestSync == true holds (which I don't think it's a reasonable coupling). From the following PRs, all E2E tests backed by Kurtosis won't assert whether doppelganger protection works as we now have a dedicated e2e test for the assertion.

Which issue(s) does this PR fix?

Part of Phase 2: Parity with "minimal" test suites

• Migrate E2E to Kurtosis #15320

Other notes for review

How to run test:

bazel test //testing/endtoend:go_doppelganger_kurtosis_test \
    --nocache_test_results \
    --test_output=all \
    --test_timeout=3600

Verified locally that this test isn't flaky.

Acknowledgements

• I have read CONTRIBUTING.md.
• I have included a uniquely named changelog fragment file.
• I have added a description with sufficient context for reviewers to understand this PR.
• I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).