[Load Testing] gherkin load test follow-up

[red-0ne]

Summary

• Add batched Proofs and batched Claims txs to support concurrent sessions
• Add Claims and Proofs counting and assertions
• Some fixes to further stabilize the tests
• Fix most of the RelayMiner's go-routine leaks

Issue

• 20

Type of change

Select one or more:

• [x] New feature, functionality or library
• [x] 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)

• [x] Unit Tests: make go_develop_and_test
• [x] 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
• [ ] I have commented my code
• [ ] I have performed a self-review of my own code; both comments & source code
• [ ] I create and reference any new tickets, if applicable
• [ ] I have left TODOs throughout the codebase, if applicable

[bryanchriswhite]

@red-0ne maybe run make trigger_ci one time as it looks like CI hasn't run since changing bases.

[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.

[Olshansk]

@red-0ne Everything is 🟢