[QoS][E2E & Load Testing] Move Service-Specific E2E Test Logic into QoS Modules

[commoddity]

Objective

Incorporate service method-specific logic that was created for the purposes of the PATH E2E & Load Tests (e2e package) into the QoS modules.

Origin Document

PR Review comments from @adshmh here:
#274 (review)

NOTE - This should be done as part of the JUDGE refactor.

Goals

Much of the logic that was created for the purposes of allowing comprehensive testing of services (for example EVM blockchains) will actually be quite valuable in performing detailed method-specific functionality inside specific QoS packages.

As an example, the EVM qos package could perform the work of:

• storing all EVM methods that could be tested (eth_getBalance, etc.)
• constructing the params for these methods
• validating both the request and response per-method

Deliverables

• QoS-applicable logic moved from e2e to qos/**
• service configurations (YAML file) moved from e2e/config/ to config

General deliverables

• Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
• Testing: Add new tests (unit and/or E2E) to the test suite.
• Makefile: Add new targets to the Makefile to make the new functionality easier to use.
• Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.

---

Creator: @commoddity
Co-Owners: @adshmh @Olshansk