chore: adds acceptance tests for debug_traceTransaction

[konstantinabl]

Description:

Adding acceptance tests covering the debug_traceTransaction endpoint

Related issue(s):

Fixes #3816

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[github-actions]

Test Results

 22 files  + 1  278 suites   - 16   18m 24s ⏱️ -36s
685 tests +18  676 ✅ +15  5 💤 ±0   4 ❌ + 3 
755 runs  +37  738 ✅ +26  5 💤 ±0  12 ❌ +11 

For more details on these failures, see this check.

Results for commit f1a634f. ± Comparison against base commit 8ff3d14.

This pull request removes 1 and adds 19 tests. Note that renamed tests count towards both.

"before each" hook for "reverts" ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender does not have enough allowance "before each" hook for "reverts"

@release should trace a successful transaction using OpcodeLogger (default when no tracer specified) ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction OpcodeLogger @release should trace a successful transaction using OpcodeLogger (default when no tracer specified)
@release should trace a successful transaction using OpcodeLogger explicitly ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction OpcodeLogger @release should trace a successful transaction using OpcodeLogger explicitly
@release should trace using OpcodeLogger with custom config (disableStack=true) ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction OpcodeLogger @release should trace using OpcodeLogger with custom config (disableStack=true)
@release should trace using OpcodeLogger with custom config (disableStorage=true) ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction OpcodeLogger @release should trace using OpcodeLogger with custom config (disableStorage=true)
@release should trace using OpcodeLogger with custom config (enableMemory=true) ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction OpcodeLogger @release should trace using OpcodeLogger with custom config (enableMemory=true)
@release should trace using OpcodeLogger with custom config (enableMemory=true, disableStorage=true) ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction OpcodeLogger @release should trace using OpcodeLogger with custom config (enableMemory=true, disableStorage=true)
should fail with INVALID_PARAMETER when given an invalid tracer type ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction Edge Cases - Parameter Validation should fail with INVALID_PARAMETER when given an invalid tracer type
should fail with INVALID_PARAMETER when given an invalid transaction hash format ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction Edge Cases - Parameter Validation should fail with INVALID_PARAMETER when given an invalid transaction hash format
should fail with INVALID_PARAMETER when given invalid TracerConfig for CallTracer ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction Edge Cases - Parameter Validation should fail with INVALID_PARAMETER when given invalid TracerConfig for CallTracer
should fail with INVALID_PARAMETER when given invalid TracerConfig for OpcodeLogger ‑ RPC Server Acceptance Tests Acceptance tests @debug API Acceptance Tests debug_traceTransaction Edge Cases - Parameter Validation should fail with INVALID_PARAMETER when given invalid TracerConfig for OpcodeLogger
…

♻️ This comment has been updated with latest results.