Tracing events

[bomanaps]

Did the basic corrections, pointed out earlier.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ bomanaps
❌ Karrenbelt
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sauliusgrigaitis]

The primary goal of the tracing is to have tracking of execution time of most of the functions in the client. The data should be visible in a convenient way - best would be to have that for each function there would be min time, max time, average and median time. I think it makes sense to implement this only for one module (for example fork_choice) just to get the feel. Please upload the numbers once you have it for running in Holesky for only one initial module. Then we can review the code and confirm that the approach is good.

[bomanaps]

Thanks for the feedback! I will begin working on implementing the tracing as you suggested.