feat: Display call parameters in the callstack table

[barabanovro]

The run API endpoint has been updated to return parameters within the callstack entries. These parameters can be found at callstack[execution_step][call_index].params.

Required Changes:

• Introduce a new column titled PARAMETERS in the callstack table.
• Display parameter values in a comma-separated row within this column.
• Display the parameter value as an array in square brackets if it consists of more than one element.
• Implement a tooltip for each parameter that shows its type_name.
• Adjust and reduce the gaps between other columns to accommodate the new Parameters column and optimize space use.

Parameters example:

[
   {
      "type_name":"RangeCheck",
      "value":[
         828
      ]
   },
   {
      "type_name":"GasBuiltin",
      "value":[
         9999999977109
      ]
   },
   {
      "type_name":"core::integer::u256",
      "value":[
         3,
         0
      ]
   },
   {
      "type_name":"core::integer::u256",
      "value":[
         5,
         0
      ]
   },
   {
      "type_name":"core::integer::u256",
      "value":[
         7,
         0
      ]
   }
]

We expect to see comma-separated Parameters row:
828, 9999999977109, [3, 0], [5, 0], [7, 0]

[jaipaljadeja]

hey i would like to do this, i recently did the virtualization changes, so i know where to add the column and rest.

[melnikga]

Can I take this?

[BlackStarkGoku]

Hi, I am a frontend software engineer that recently discovered starknet ecosystem! I really want and I am motivated to start doing my first contributions to the ecosystem, I would be honored to tackle this issue by looking at what the result of this API is about and making all changes needed !

[barabanovro]

Thank you everyone for your interest in working on this issue. I am assigning it to @melnikga, who has the capacity and relevant experience to address this promptly.