feat(trace): callTracer add revert reason

[jsvisa]

Description

backport from go-ethereum, add revertReason for the callTracers

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also
list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Go Version:
• Hardware:
• Docker Version:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• New and existing E2E tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have not added any vulnerable dependencies to my code

[jsvisa]

@freemanzMroj @otherview PTAL, thanks.

[otherview]

Hey @jsvisa thank you for the collaboration, but the team ruled out this PR, the reason being that the team decided it's preferable to leave revert reason interpretation to the contract consumer (user).

If you feel strongly about this, please raise an issue, and we can kickoff a more broad discussion.
Many thanks!

[jsvisa]

Hi @otherview this field is backported from go-ethereum https://github.com/ethereum/go-ethereum/blob/08e6bdb550712503873fb2a138b30132cc36c481/eth/tracers/native/call.go#L59

Hey @jsvisa thank you for the collaboration, but the team ruled out this PR, the reason being that the team decided it's preferable to leave revert reason interpretation to the contract consumer (user).

As the output is byte encoded, I think the decoded string should be more readable for the consumers to identify why the tx was failed or call failure.