Added option to disable structLogs for debug_trace* rpc methods.

[ohijiho]

Description

The easiest reliable way to get return data of a transaction is debug_traceTransaction rpc, but it comes with huge structLogs data, which uses a lot of network traffic.

This is a simple solution for that: Just add an option to disable it.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

Manual tests

1. Start the chain
2. Make a transaction
3. Call trace_debugTransaction with disableLogs set to true and then false.
4. Check that structLogs field is filled only when disableLogs is set to false.

Additional comments

I removed some test code lines that skips certain test suites. I don't know exactly why they have been made skipped originally, but they seems to work well now.

[vcastellm]

LGTM

[dusan-maksimovic]

LGTM. Perhaps we should align all the flags in TraceConfig so we don't have half of them be EnableXYZ and the other half DisableXYZ. But this can be done through some other PR.

[Stefan-Ethernal]

so we don't have half of them be EnableXYZ and the other half DisableXYZ

@ohijiho I agree entirely with @dusan-maksimovic here. Also then it makes more sense to expose the EnableMemory, EnableStorage, and EnableStack fields, and no need to have DisableStructLogs in general. WDYT?

[ohijiho]

so we don't have half of them be EnableXYZ and the other half DisableXYZ

@ohijiho I agree entirely with @dusan-maksimovic here. Also then it makes more sense to expose the EnableMemory, EnableStorage, and EnableStack fields, and no need to have DisableStructLogs in general. WDYT?

Then, structLogs is disabled by default and enabled when one of memory, storage or stack is enabled? If that's the case, the config will be restricted so that there's no option to enable only the structLogs.

FYI, the main purpose of this PR is adding an option to entirely disable the structLogs, which is different from disabling all three extra informations.