Add SNAX specific events to the tracing script

[AntonLydike]

Adds SNAX specific event tracer to the trace_to_perfetto utilty:

The following three events are discerned to produce those traces:

• a "pre-launch" event, that:
  - starts at the first CSR write to a config register
  - ends after all launch fields have been written to
  - records the number of setup instructions executed
• a "launched but not waiting" event, that:
  - starts immediately after the "pre-launch" event
  - ends on the second "write 0 to launch addr"
• a "waiting" event, that:
  - starts on the first read from the barrier address
  - ends when that read return 1

This should be general enough to support any SNAX accelerator, although I (@JosseVanDelm) am not entirely sure how to verify that in CI.

The utility was already useable standalone, but this patch makes it more difficult to specify a bunch of options that are invalid.

• You can now use --sequential to run the tracer in sequential mode, which is useful for debugging with pdb.
• You can use --accelerator to specify a SNAX accelerator in order to activate the SNAX specific event tracer (this functionality is also now available for process_traces in SNAXBenchmark.
• Kernel annotation is now optional with --annotate-kernels and the tool will warn you if you do not specify the --elf-file and the --addr2line executable

Important note:
In perfetto you might want to change your time format to be anything but timecode, because otherwise it seems to mess up the numbers (not sure why, and also not sure how we can change that default behaviour)

[JosseVanDelm]

@AntonLydike I rebased this, found a few errors, and added some functionality

[JosseVanDelm]

This was a bit wrong before 😄 :

            if ins.csr in self.fields or self.launch_fields:

Which is almost always true 😅

[JosseVanDelm]

@AntonLydike I can not request a review from you, but I'd appreciate it if you could have a look at this :)