EVM/Benchmarks: improve opcode benchmarks to output ticks-only datas

Context

As explained in !11611 (merged), we discovered that the tick model for SSTORE is actually constant. This MR adds two things:

1. Add an argument to the benchmark script to remove the flamecharts, as the debugger fails if there is not enough space in /tmp
2. Add some columns to the analysis of the opcodes containing the average ticks per opcode and the standard deviation.

Manually testing the MR

As running the benchmarks are quite long (5-6h with a good hardware), let me give you a dump of the opcode with master at the moment the branch was created:dump_opcodes_2024-01-19T06-56-20.541Z.json

You can then run the analysis with

node etherlink/kernel_evm/benchmarks/scripts/analysis/opcodes.js dump_opcodes_2024-01-19T06-56-20.541Z.json

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR