[Testing] Stress / load test ephemeral & persistent chains

[red-0ne]

Summary

Make the necessary adjustments to the load test framework to be able to run on persistent chains.

Issue

The load testing framework was not able to run without scaling Gateways and Suppliers. Which is not the goal for testing persistent chains like DevNet and TestNet.

• 531

Type of change

Select one or more:

• [x] New feature, functionality or library
• [ ] Bug fix
• [ ] Code health or cleanup
• [ ] Documentation
• [ ] Other (specify)

Testing

Documentation changes (only if making doc changes)

• [ ] make docusaurus_start; only needed if you make doc changes

Local Testing (only if making code changes)

• [ ] Unit Tests: make go_develop_and_test
• [ ] LocalNet E2E Tests: make test_e2e
• See quickstart guide for instructions

PR Testing (only if making code changes)

• [ ] DevNet E2E Tests: Add the devnet-test-e2e label to the PR.
  • THIS IS VERY EXPENSIVE, so only do it after all the reviews are complete.
  • Optionally run make trigger_ci if you want to re-trigger tests without any code changes
  • If tests fail, try re-running failed tests only using the GitHub UI as shown here

Sanity Checklist

• [x] I have tested my changes using the available tooling
• [x] I have commented my code
• [x] I have performed a self-review of my own code; both comments & source code
• [x] I create and reference any new tickets, if applicable
• [x] I have left TODOs throughout the codebase, if applicable

[Olshansk]

@red-0ne Please re-request review and update PR title when this is ready.

[red-0ne]

• Separated (non-)ephemeral config parsing validation.
• Now we have different manifest for ephemeral and non-ephemeral tests.
• Added Makefile targets for each of the ephemeral and non-ephemeral tests.
• Moved the manifest from the root directory to load-testing

Possible improvement:

Be able to specify the test plan (feature files) to execute from the manifest file

[red-0ne]

@Olshansk , I think the address/keyName issue is creating a lot of ambiguity. Will take some time to get rid it by only relying on addresses.

[Olshansk]

@red-0ne Love the simplification, so much clearer now!

Only big remaining question is whether we need both address and accAddress in accountInfo.

I know I can pull the PR and figure it out myself but just asking to expedite things.

[red-0ne]

@Olshansk , accAddress removed successfully

[github-actions[bot]]

The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks. If you just created a pull request, you might need to push another commit to produce a container image DevNet can utilize to spin up infrastructure. You can use make trigger_ci to push an empty commit.