Improve cycles output in analyze tool

[Fumuran]

This PR adds extended information about traces lengths of VM components to the analyze tool output.

[bobbinth]

Looks good! Thank you! I left a couple of minor comments inline. After these are addressed, we can merge.

Also, could you paste a screenshot of how the output for this looks like?

[Fumuran]

Now analyze output for the merkle_store example looks like this:

and similar output for the fibonacci example:

I added variable width for the first column, so operations names will always fit (for example, before that push.*.*.* operations from merkle_store example were breaking the table). I also added the line to highlight the table header.

[bobbinth]

Looks great! A couple of minor comments on the output formatting:

1. Let's move "Total number of NOOPs executed" after the table.
   a. Also, let's not capitalize "number".
2. For the table, let's rename "AsmOp" title into "Assembly instruction"
3. Above the "VM cycles" section, let's add a header "Analyzed [program name] with [input name]".

Basically, the output could look like:

============================================================
Analyzed fib.masm program with fib.inputs

VM cycles: ...

Assembly Instruction ..
--------------------------

Total number of NOOPs executed: 

[Fumuran]

After last refactoring output looks like this:

[bobbinth]

Looks good! Thank you! One last thing: could we add:

============================================================

Before the Analyzed... line?

[Fumuran]

The final view:

[bobbinth]

All looks good! Thank you!