Revise and optimize the RPC method trace_callMany

[rubo]

Fixes #4165. Closes #4419.

Changes:

This is a revised and optimized version of PR #4419.
This also changes trace module from arrays to enumerables to avoid unnecessary allocations.

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests??

• Yes
• No

Besides unit tests, the changes have been tested on Goerli as follows:

1. Transfer funds from account A to an unused account B and then back to account A. Succeded as expected.
2. Transfer funds from account A to account B and then from an unused account C to account A. Failed as expected.

[rubo]

@LukaszRozmej Geth uses debug_traceCall naming. I'm not sure how our naming aligns with the Debug module standardization.

[tanishqjasoria]

@LukaszRozmej Geth uses debug_traceCall naming. I'm not sure how our naming aligns with the Debug module standardization.

this call is part of the trace module that openethereum introduced: https://openethereum.github.io/JSONRPC-trace-module

[LukaszRozmej]

@LukaszRozmej Geth uses debug_traceCall naming. I'm not sure how our naming aligns with the Debug module standardization.

debug and trace modules are different things and use different formats.

[LukaszRozmej]

Could you also smoke test other changed tracing methods (they should be fine, but...)